Demystifying Software Architecture: Monolith vs. Micro-services

Monolithic architecture often offers simplicity in development and deployment, making it a common choice, especially for startups or smaller applications. However, as applications scale and become more complex, the benefits of a micro-services architecture — such as independent deployment, technology diversity, and enhanced fault isolation — become increasingly appealing.

This presentation will be delivered at #41 TechTalks by Widya Analytic

Transcript

1. #41 TechTalks Monolithic vs Microservices Which one is better? Muhammad Yusuf Manshur Software Engineer at Widya Analytic
2. What is the primary goal of software?
3. OSI Models
5. Contents Monolithic 01 What is Monolithic architecture Microservices 02 What are Microservices architecture Differences 03 Discuss the differences and advantages of the two architectures When is it 04 When is it appropriate to use Monolithic or Microservices architecture
6. Monolithic Monolithic application has single code base with multiple modules. It has single build system which build entire application and/or dependency.
8. Key Characteristics of Distributed Systems
9. Microservices Involves smaller applications deployed independently as loosely coupled services, tied together through application integration. From a software engineering perspective, microservices can be simpler to develop.
10. How does Microservices works? • Synchronous ◦ REST, RPC • Asynchronous ◦ Common Data ◦ Double Queue (request-response) ◦ Event Driven Architecture ◦ etc. • Database per service (recomended) • Shared Database Communication Patterns Database Patterns
11. Direct Call or Remote Procedure Call (RPC) Source: https://techdozo.dev/grpc-synchronous-and-asynchronous-server-streaming-rpc/
13. Shared Database
14. Shared Database
15. How do you build Microservices? The following are the key points to think about at that time. 1. Divide data into bounded contexts or data domains. 2. Keep communication between services simple. 3. Build your microservices architecture for failure. 4. Emphasize monitoring to ease microservices testing. 5. Embrace continuous delivery to reduce deployment friction
18. Why using Monolithic? Source: https://www.qulix.com/about/monolithic-vs-microservices-architechture/
19. Why using Microservices? Source: https://www.qulix.com/about/monolithic-vs-microservices-architechture/
20. Microservices mean you will have farms, not pets.
21. Distributed Monoliths vs. Microservices: Which Are You Building? Distributed Monolith is a system that resembles the microservices architecture but is tightly coupled within itself like a monolithic application. Most people misunderstand the concept of microservices
22. Running microservices is not a sprint Should be seen as a journey rather than the immediate goal for a team. Start small to understand the technical requirements of a distributed system, how to fail gracefully, and scale individual components
23. Role #1 Don’t use Microservices
24. CREDITS: This presentation template was created by Slidesgo, including icons by Flaticon, and infographics & images by Freepik Thanks Please keep this slide for attribution