filmov
tv
Microservices in 60 mins | Learning Path & Interview Preparation
![preview_player](https://i.ytimg.com/vi/v_ABLktEwRU/maxresdefault.jpg)
Показать описание
In this video, We will learn about different design patterns and tools used in Microservices.
We also covered a popular microservices interview question :
Tell me about the tools and design patterns that you have used in microservices.
When it comes to Microservices , A developer is involved right from creating Microservices to deploying it cloud, hence understanding the each phase of the Microservices development is important.
Defining Microservices Boundaries
——————
When we create a Microservice, the first thing that we do is define the boundary of our Microservice (Bounded Context). For an example a sms-service should have sending sms related scope inside the project. It should not deal with the Payment processing stuffs inside the same project. That’s why defining the boundary for a Microservices plays a very important role, when it comes to maintainability of code.
Microservices Communication
————————
All our Microservices should communicate with each other. In order to make this communicate happen, we can use RESTful web services, Messaging service, Event streaming etc. Apache Artemis, Active MQ, Rabbit MQ, Kafka are some popular message brokers
Microservices Deployment
—————
Virtual machine might not be an Ideal solution for the Microservices deployment. Even Though VM’s are widely used in industry, But creating a VM is a tedious job as it involves a manual process of
1. Distribution or memory
2. OS installation
3. Library installation etc
As a Virtual Machine Involves an Operating System, It’s not fast to bootstrap and shutdown. So it doesn’t help much in a Microservices environment , where we need quick deployment of our Microservices when the load increases. We also need a autoscaling feature where we can automate our Microservices deployment. Here the Docker and kubernetes comes handy. We can replace our VM’s with container which doesn’t involve an OS and pretty fast in comparison to VM.
Microservices Design Patterns
———————————
Microservices Architecture helps us to split our huge monolith application to pieces and makes the developer life easy. But with this simplicity, there comes a lot of responsibility and challenges. To help us solve the challenges, We have proven design pattern.
1. With a handful of Microservices, We need to manage a lot of server where these Microservices are deployed. To manage these server ip’s we use a design pattern called service discovery and registration design pattern.
2. Our Microsrvices should be fault tolerant. To make our Microservices resilient, We use design patterns like Circuit breaker design pattern, Retry Pattern, Bulk Head pattern, Rate Limiter pattern etc.
3. To address cross cutting concerns like Security, Logging,Tracing; We use a design pattern called Gateway design pattern.
4. To Manage distributed Transaction, We use Saga design pattern.
5. There are other design patterns concepts like Load balance, DDD, CQRS, Event Driven etc which can helps boosting the performance of our Microservices application.
We have discussed all of these in this microservices roadmap video and you can use the timestamp to navigate to different microservices tool and design patterns KT.
Timestamp
------------------
Into - 00:00
monolith vs microservices - 01:38
What are microsrvices - 03:56
DDD / Define Microservices Boundaries - 05:04
Microservices Communication - REST API
Service Discovery & Registration pattern - 10:43
Message Brokers - 14:29
Event Streaming with Kafka - 17:51
Single Database per Microservices - 20:34
Microservices Deployment ( Docker & kubernetes ) - 22:19
What are Virtual Machine (VM) - 24:12
Load Balancer - 26:25
What are containers - 29:23
Virtual Machine Vs Container - 33:54
Distributed transaction in microservices- 33:44
Learn Saga Pattern - 41:07
The gateway pattern - 43:34
Handling Microservices Failure - 48:31
microservice resilience patterns - 49:33
The circuit breaker pattern - 51:49
Microservices free course - 57:09
microservices free course :
Microservices paid course :
For more free/paid courses visit
Watch my new mock interview series for java developers
Watch my new Hello spring boot series
Spring Framework course
Any time you are getting stuck with issues, Feel free to ask for support.
you can ping me on my Facebook page
Make sure to join my private Facebook page (Ask me here)
“SeleniumExpress - Support"
Follow me on Insta
We also covered a popular microservices interview question :
Tell me about the tools and design patterns that you have used in microservices.
When it comes to Microservices , A developer is involved right from creating Microservices to deploying it cloud, hence understanding the each phase of the Microservices development is important.
Defining Microservices Boundaries
——————
When we create a Microservice, the first thing that we do is define the boundary of our Microservice (Bounded Context). For an example a sms-service should have sending sms related scope inside the project. It should not deal with the Payment processing stuffs inside the same project. That’s why defining the boundary for a Microservices plays a very important role, when it comes to maintainability of code.
Microservices Communication
————————
All our Microservices should communicate with each other. In order to make this communicate happen, we can use RESTful web services, Messaging service, Event streaming etc. Apache Artemis, Active MQ, Rabbit MQ, Kafka are some popular message brokers
Microservices Deployment
—————
Virtual machine might not be an Ideal solution for the Microservices deployment. Even Though VM’s are widely used in industry, But creating a VM is a tedious job as it involves a manual process of
1. Distribution or memory
2. OS installation
3. Library installation etc
As a Virtual Machine Involves an Operating System, It’s not fast to bootstrap and shutdown. So it doesn’t help much in a Microservices environment , where we need quick deployment of our Microservices when the load increases. We also need a autoscaling feature where we can automate our Microservices deployment. Here the Docker and kubernetes comes handy. We can replace our VM’s with container which doesn’t involve an OS and pretty fast in comparison to VM.
Microservices Design Patterns
———————————
Microservices Architecture helps us to split our huge monolith application to pieces and makes the developer life easy. But with this simplicity, there comes a lot of responsibility and challenges. To help us solve the challenges, We have proven design pattern.
1. With a handful of Microservices, We need to manage a lot of server where these Microservices are deployed. To manage these server ip’s we use a design pattern called service discovery and registration design pattern.
2. Our Microsrvices should be fault tolerant. To make our Microservices resilient, We use design patterns like Circuit breaker design pattern, Retry Pattern, Bulk Head pattern, Rate Limiter pattern etc.
3. To address cross cutting concerns like Security, Logging,Tracing; We use a design pattern called Gateway design pattern.
4. To Manage distributed Transaction, We use Saga design pattern.
5. There are other design patterns concepts like Load balance, DDD, CQRS, Event Driven etc which can helps boosting the performance of our Microservices application.
We have discussed all of these in this microservices roadmap video and you can use the timestamp to navigate to different microservices tool and design patterns KT.
Timestamp
------------------
Into - 00:00
monolith vs microservices - 01:38
What are microsrvices - 03:56
DDD / Define Microservices Boundaries - 05:04
Microservices Communication - REST API
Service Discovery & Registration pattern - 10:43
Message Brokers - 14:29
Event Streaming with Kafka - 17:51
Single Database per Microservices - 20:34
Microservices Deployment ( Docker & kubernetes ) - 22:19
What are Virtual Machine (VM) - 24:12
Load Balancer - 26:25
What are containers - 29:23
Virtual Machine Vs Container - 33:54
Distributed transaction in microservices- 33:44
Learn Saga Pattern - 41:07
The gateway pattern - 43:34
Handling Microservices Failure - 48:31
microservice resilience patterns - 49:33
The circuit breaker pattern - 51:49
Microservices free course - 57:09
microservices free course :
Microservices paid course :
For more free/paid courses visit
Watch my new mock interview series for java developers
Watch my new Hello spring boot series
Spring Framework course
Any time you are getting stuck with issues, Feel free to ask for support.
you can ping me on my Facebook page
Make sure to join my private Facebook page (Ask me here)
“SeleniumExpress - Support"
Follow me on Insta
Комментарии