Microservices and Modularity or the difference between treatment and cure!
summary
Argues that microservices often shift complexity to infrastructure rather than remove it and shows a concrete refactor of the Dukes store: extract a domain model and use cases, reorganize Maven modules, then reuse that core to produce a Spring Boot REST microservice, OSGi bundles running on Felix, a remote OSGi service, and a Liferay portlet, all sharing the same logic. Recommends clean architecture as treatment not cure and cites a production portal of five million lines using OSGi.
AI-written summary · about
chapters (11)
- 0:00Start
- 1:55What Are Microservices
- 3:02Why You Would Like To Use Micro Services
- 6:54Who Is Using Micro Services
- 8:59Should You Use Micro Services or Not
- 10:16Microservices Are Not the Cure
- 11:32Treatment for Complexity
- 17:27The Domain Model
- 25:14Jar Files into Osgi Bundles
- 27:53Create a Rest Endpoint in Osgi
- 40:50Osgi
related talks
47mModular Monoliths
52mWhat Does a Good Microservice Architecture Look Like?
55mIs it Time to Abandon Microservices? Modular Monoliths Rescue Your Wallet!
51mModularization: Foundation of Microservices and Monoliths
38mMicroservices, a bittersweet symphony
52mMicroservices & the Inverse Conway Maneuvre
01mModularization: Foundation of Microservices and Monoliths
46mModular Applications with Spring