The Reason to Use Microservices
- 1. The Reason to Use Microservices Dmytro Bischak 2017
- 2. About Author First microservice application in 2004 Windows C++ services on Pipes
- 3. Microservices vs Monolith Dashboard Service Tracking Service Marketing SystemCampaign Service Report Service
- 4. Goals of Microservices Loose coupling Independence in development Independence in technology Better scaling
- 5. Overhead of Microservices Deployment Monitoring Additional code Communication between services
- 6. Challenges of Microservices Service Discovery Service Versioning Load balancing and availability
- 7. Advices Frameworks (e.g. Lagom, Spring Cloud) Don't use Microservices in the first system Use small number of services
Editor's Notes
- #3: I created my first microservice application in 2004. It was C++ server application for Windows for control cash registers. The application used interprocess communication between microservices, that implemented on Pipes. But of course, I did not know about the concept of Microservices. The concept of Microservices is not new.
- #4: Monolith architecture is architecture when all features/functionalities implemented in one application. Microservices architecture is architecture based on a set of separate services.