Speaker 1: Every day we are building microservices, but have you ever thought about defining the boundaries of microservices, defining the communication protocol for microservices or after building the microservices, how we are going to deploy it, how we are going to scale it, how we are going to monitor it, how we are going to secure the microservices. All these are different aspects which we need to consider before even putting a basic design about microservices. So, here I am Tarun Sarma, I'm going to help you and guide you about all these different design aspects of microservices, which are like communication, logging, monitoring, deployment and DevOps, service composition, security, fault tolerance, and service discovery. different architecture pattern which you might consider before designing a service. Let's say if I'm designing a microservice today, so what all are questions I will ask before I start writing code. I will identify the service, define the boundaries and first of all choose the communication protocol which I'm going to use. It can be synchronous or asynchronous, if it is synchronous then protocols will be maybe REST or gRPC, maybe TCP and you can see REST and gRPC I will define contract, I will define in API spec, and then implement a service. But on the other side, if it is asynchronous, then I will be using some message broker. I can choose broker from the Kafka, Revit MQ, or maybe SQS SNS. And then here, if it is Kafka, I will define topics, define queues. I will write my service, and then I will deploy my microservice. But the real game will start right after this, right? So till now, we just created a service, But now we need to take care of monitoring, scaling, deploying, security, and all these different critical aspects of a microservice. These are the different aspects. I will think about designing a microservice, logging and monitoring. I deployed my microservice. Then I now need to take care of logging and monitoring. Here how I'm helping in that, so I have a playlist which I will be adding logging with the maybe ELK stack, logging with the CloudWatch, logging with the Grafana and Prometheus, that I'm going to cover here. So let's say we are writing a Node.js, NestJS, basic logging, creating a custom logger, log analysis, monitoring setup, all these things will be inside this playlist. Okay. Coming to the testing part, testing we are already using Jest and for performance testing you can use artillery or you need an integration and end-to-end test we can just use jest and you're where you can do unit test and API test data management I mean till now we just either use a sequel or no sequel database so we can stick to that now scalability scalability I haven't touched this particular point but with microservices we will be talking about this a lot it can be a separate playlist which talks about scalability of of microservices. Load balancing, putting a proxy and scaling. I mean, putting a load balancer just by using Nginx. Putting a load balancer by just putting application load balancer on AWS, or a horizontal scaling or a vertical scaling of your microservice, either a Node.js, NestJS. When you are deploying your service either on EC2, either on the container ECS, or maybe on the Kubernetes. Another is different architecture pattern to provide a resilience and fault tolerance like having a retry mechanism or fallback mechanism so that we can always have a fallback when there is a fault tolerance and when there is error happens. Security, I already have started a playlist which talks about authentication and authorization. This is the one where we will be talking about all different type of authentication and authorization for any microservice either using external tool like Auth0, Firebase or social provider login or your in-house based on cookies sessions during the session in the redis so that we can maintain the state of JWT token if there is a need of having that and deployment continuous integration I have covered somewhere I will collect those so we will be talking about CI CD using GitLab CI GitHub actions and then containerization and infrastructure as a code I will be talking first time about kubernetes in this playlist where we will talk about Containerization is simple with the docker. Docker local setup with the maybe with the docker compose you are able to spin up some containers. But containerization with the kubernetes that's a different thing, right? Infrastructure as a code which we have already done with the CDK stack, right? AWS CDK stack we have used where I was able to deploy a simple lambda to AWS, right? And then you can also spin up other AWS resources using that. This is another playlist. i will be collecting the videos and i will be adding the brand new videos why i'm all doing all these things because i want to create a clean structure for all the micro service design aspect into separate playlist okay inter service communication we have covered rest grpc messaging queues event driven i have i am covering all these micro services nest js based micro services which are exposing rest interface using grpc, kafka, revit mq, providing a communication using event-driven or a simple synchronous either using grpc and tcp or rest api using http protocol that i will be aggregating and will be making available for you all guys service composition so this is like which everybody is asking me that i need to implement either domain-driven design or bounded context or hexagon hexagonal context hexagonal based architecture design of a services and service registry and service discovery. I will also cover on top of that the different architecture pattern which I already have covered but I will I'm going to create a segregate aggregate playlist which contains only those videos so you can see what are the new playlist coming up on my channel and all are interesting All are covering Nest, GS, Node, GS, and only talking about microservices. Either it is a scalability, data management, testing, security, deployment on different platform, inter-service communication, and exposing a different interface through your APIs, different type of communication, microservices using a different type of protocols. But that's a lot. And don't worry, I'm not going to cover everything like parallel or in one go. Currently, we are talking about logging and monitoring. What is my next topic? You can expect. I'm going to cover ELK stack with an SCS Node.js like how I can use Elasticsearch logs-kibana for visualizing the logs, aggregating the logs in a particular microservice. Okay. That's it, guys. Thanks, everyone.