Microservices Architecture Pattern
From the collection Architectural Patterns in Software Engineering

microservice
architecture
pattern

Microservices Architecture Pattern

You can show this QR Code to a friend or ask them to scan directly on your screen!

Thanks for sharing! 🫶

The url for this was also copied to your clipboard!
The collection of small services that are combined to form the actual application is the concept of microservices pattern. Instead of building a bigger application, small programs are built for every service (function) of an application independently. And those small programs are bundled together to be a full-fledged application. So adding new features and modifying existing microservices without affecting other microservices are no longer a challenge when an application is built in a microservices pattern. Modules in the application of microservices patterns are loosely coupled. So they are easily understandable, modifiable and scalable.  

Advantages:
  1. Scalability: Each service can be scaled independently based on demand.
  2. Faster Delivery: Independent services allows teams to develop, test, and deploy features faster.
  3. Easier Maintenance: Services can be updated and maintained independently.

Disadvantages:
  1. Complex Management: Managing multiple services requires robust monitoring and management tools.
  2. Network Congestion: Increased network traffic between services can lead to congestion and overhead.
  3. Security: Securing multiple services and their communication increases the probability of attack.

Use Cases:
  1. E-commerce Platforms like Amazon and eBay.
  2. Streaming services like Netflix and Spotify.
  3. Online Banking Platforms.
  4. Electronic Health Record (EHR) Systems.
  5. Social Media Platforms like Twitter and Facebook.

e-commerce
See more from etori.sangiacomo