Lallan Kumar

basically, I'm use asset property in MongoDB. It is not inbuilt. I will make by using fallback, in my groceries. Yeah. Thank you.

Basically, before moving on production, create a different environment where, the architecture will be would be moved into microservice by using different services, like, database management, how the fallback will manage if any transaction would happen, how the API will API speed increase by using Redis or other some cache. And once all things will be completed, need to go for a QA approval. After that, all could be pushed on production without deleting or, any data. Thank you.

basically, for high availability, Namo, what do we I can use scalable application. Like, EKS, I can use here where, if user is more than the that, we have defined, then the application would be auto scaled, and, we can use throttling as well as so if any user got the response, got the API and want to, call again and again like a hacker, that can be break as well.

in a heavy read and write loads, we can use cluster as well as with the we can use auto scaling, and we can use queue management where we can write the application. We can where we have a right query, we can do we can use a different write technique, and, we can also use read as well. Like, MongoDB clusters, we can use. And, replica, we can use, where read has a different port and write has a different port. Because read, maximum time, we are using read approaches. and somehow, we can also use write. So we need more latency in data, but, right approach, we can use queue as well.

What are the key features in there? in microservice architecture, we can use, like, we can share data between services, with using if you want a real time data from different services, we can use gRPC. and if you want data like a trans we can use transaction. At that time, we can use a queue management like a Kafka or RabbitMQ, where after an after transaction, we can give the response, with using socket. we can use different database and sorry. We can use different database for each services, and we can also use Redis for, like, where we want instant response, like profile API would use multiple times. So we can try with the profile API in Redis. Once everything anything will be update in user side, the Redis also get updated. And, we need to write, we need to write a code there. reader application will work differently and write a question will work differently. so that, all load will not go to on same port, right, like a replica. We can use here.

We'll just, in this case, we need to update the status code 500 to 400 because 500 will throw a server error, internal server error. We need to change from 500 to 400 in cache. And we need more we need to add more things like, if user has authenticated, we need to add logic more authentication lock in here.

Connection pooling. in connection pooling, if, we need to create a connection pool because, if we do not write, we do not manage as a connection pooling. The connection has been started, and, after the, process has been completed, the load the connection will be break there. At the time, sometime, it will cause us some error so that we need to write maximum connection pulling, in a particular instance so that any unwanted user cannot attack on the particular instance.

Steps. We need to add a gRPC for inter servers service communication. basically, GRPC will transfer data within the components in the form of buffer. that will not be easily to read, whenever data is communicating communicated within the server. And, we need to if we are using different server or different instance, we need to just add the application, in the server side. Only that time will be called, when the server is calling from, the particular API. Otherwise, it will not respond. It will throw error. So that will also secure the, microservice architecture as well.

basically, we need to, we need to write we need to work with the when we are working with the MongoDB, we need to write a master slave method. basically, in this method, if any master or any slave will would not any master would not work, the other slave automatically work as a master and, automatically shift the whole control to that. in master control, all things will be worked as a, like, they can handle read as well as write operation and execute. But in slave, they can only read. So we can use the master slave protocol, master slave method as well.

We can create a, we can, we can create a replica for that time. when we are interacting with the AWS, we can create replicas. That's why, if one replica is not working, others will automatically, worked. So that's the good practice for that.