Why Would You Move to Micro-services?
I have been managing projects following Microservices Architecture pattern which was developed on top of Adapter Design Pattern. When someone asked me why are you on Microservices I always made it complicated (I think : ) while I explained it to them) — but below blurb is the simplest explanation of this hence pining it.
— — — — — — — — — — — — — — -
Applications are made of multiple components. The components communicate with each other to transmit data, fulfill requests, and keep the application running.
Suppose that you have an application with tightly coupled components. These components might include databases, servers, the user interface, business logic, and so on. This type of architecture can be considered a monolithic application.
In this approach to application architecture, if a single component fails, other components fail, and possibly the entire application fails.
To help maintain application availability when a single component fails, you can design your application through a microservices approach.
In a microservices approach, application components are loosely coupled. In this case, if a single component fails, the other components continue to work because they are communicating with each other. The loose coupling prevents the entire application from failing.
When designing applications on AWS or any other Cloud, you can take a microservices approach with services and components that fulfill different functions.
With AWS it’s easier as they have two services facilitate application integration: Amazon Simple Notification Service (Amazon SNS) and Amazon Simple Queue Service (Amazon SQS).
Learned from AWS Cloud Practitioner Essentials Course!
