They are basically three patterns to scale your micro services
- API gateway pattern
- We place API gateway in front of micro services, so client know only about API gateway. Rest of the communication pipes are hidden from the client.
- API gateway performance authentication, request /responselogging or throttling.
- Service Mesh
- Service mesh is a software driven approach to route and segment data among microservices.
- The goal is to solve the networking and security challenges of opting micro services and cloud infrastructure.
- It provides failure handling, retries, And network observe-ability.
- Service mesh is a distributed API gateway pattern.
- The traffic can also move among the micro services without involving gateway.
- The traffic is distributed among micro services.
- The function of routing, logging and rate limiting To operate in distributed session, is faster.
- We complied this using site cars
- A site car is attached to payment micro service, which enhances its functionality.
- The site called abstract, the common functionality of micro services to a different layer.
- We do not need to write configuration code in each and every micro service
- It provides loose coupling between the application code and platform.
- Site cars is a library that grow their own environment.
- Event driven Approach
- The event is driven by one micro service and on the occurance of event, other micro service responds.
- The micro service subscribe to event notification.
- The micro service is notified once the piece of information is ready.
No comments:
Post a Comment