Microserices - Not a Binary Choice
SATHISH KUMAR THIYAGARAJAN
Chapter 1: The Great Debate
The Challenges
team is struggling to stay productive
application isn't scalable enough
your response times are sluggish
hard time clearing those job interviews
Microservices
The Transformation
Monolith
Microservices
Modular Monolith
Chapter 2: A Cautionary Tale
The Outcome
Cost
Complexity
Lack of Standard
Performance: APP and Team
Only for rich ?!
Chapter 3: Monoliths and Microservices as Families
Monolithic
Microservices
Easy to Split. But Reunion ?!
Chapter 4: Microservices: Deconstructing the Vada Pav
Recommendations
- Monolith is not a bad approach if it works properly. In some cases, a monolithic architecture can be sufficient to meet the needs of the application and its users.
- It's generally not advisable to start a new project using a microservices architecture. This approach adds complexity and can be challenging to manage, especially for smaller teams.
- It's better to develop the application as a monolith and then consider deploying it as microservices if necessary. This approach allows for easier testing, debugging, and development, while also allowing for easier deployment and scaling in the future.