What does a typical the microservice architecture look like?

161 viewsSystem Design

What does a typical the microservice architecture look like?

1). What are the drawbacks of the microservice architecture?
2). Have you seen a monolithic system be transformed into microservice architecture? How long does it take?

Please explain the microservice architecture.

Farjanul Changed status to publish September 5, 2022

The diagram below shows a typical microservice architecture.

Load Balancer: This distributes incoming traffic across multiple backend services.

CDN (Content Delivery Network): CDN is a group of geographically distributed servers that hold static content for faster delivery. The clients look for content in CDN first, then progress to backend services.

API Gateway: This handles incoming requests and routes them to the relevant services. It talks to the identity provider and service discovery.

Identity Provider: This handles authentication and authorization for users.

Service Registry & Discovery: Microservice registration and discovery happen in this component, and the API gateway looks for relevant services in this component to talk to.

Management: This component is responsible for monitoring the services.

Microservices: Microservices are designed and deployed in different domains. Each domain has its own database. The API gateway talks to the microservices via REST API or other protocols, and the microservices within the same domain talk to each other using RPC (Remote Procedure Call).

Benefits of microservices:
– They can be quickly designed, deployed, and horizontally scaled.
– Each domain can be independently maintained by a dedicated team.
– Business requirements can be customized in each domain and better supported, as a result.

Farjanul Answered question September 5, 2022