01 Microservices Material
01 Microservices Material
Ashok
Microservices Development
=> Software Applications we can develop in 2 ways
1) Monolithic Architecture
=> If we develop all the functionalities in single application then it is called as Monolithic Application.
1) Presentation Layer
2) Business Layer
=> To overcome problems of Monolith Architecture, we will use Micro services Architecture.
Microservices Introduction
=> It is not a technology
=> It is universal pattern and anyone can use this architecture to develop applications using any
technology.
1) Bounded Context
2) Repeated configurations
3) Visibility
=> Bounded context means identifying how many micro services we need to develop for one
application and deciding which functionality we need to add in which micro service.
=> In Several micro services we need to write same configurations like data source, smtp, kafka,
redis etc.
=> In micro service architecture we might not get chance to work with all apis in the application.
Microservices Architecture
=> There is no fixed architecture for micro services development.
=> We can customize micro services architecture according to our project requirement.
=> As part of Micro services architecture we are going to use below components.
(all the below components are not mandatory, we can use them based on demand)
Service Registry
=> Service Registry is used to maintain all apis information like name, status, url and health at once
place.
Admin Server
=> It is used to monitor and manage all the apis at one place.
=> It provides beautiful user interface to access all apis actuator endpoints at one place.
Zipkin Server
Config Server
=> It makes our application loosely coupled with properties file or yml file.
Feign Client
=> If one api communicate with another api with in the same application then it is called as Inter
service communication.
Kafka Server
Redis Server
API Gateway