One Microservices is no microservice: They come in systems
summary
Argues that microservices only make sense as distributed systems and that naive REST-chaining fails; proposes Light Bend’s logum platform (Scala-built, Java API first) that boots a local dev environment—cassendra, service locator and gateway—via SBT and can scale to many services. Recommends CQRS and event sourcing for fast read/write paths, embraces eventual consistency with compensating events, and claims developer experience and deployment wiring are solved by the opinionated framework.
AI-written summary · about
chapters (23)
- 0:00Intro
- 1:06Microservices is a big topic
- 2:03Application servers
- 3:54What does it mean
- 5:24monolithic applications
- 7:26business value
- 10:08Rest
- 12:13Build systems
- 12:32Gartner quote
- 13:06Ive been an architect
- 13:58Theres nothing rocket science
- 14:56How do we get there
- 21:23Flexible systems
- 21:58React manifest
- 22:28Offstage
- 23:23Developer experience
- 24:53Production
- 25:58Logon
- 27:18Streaming between services
- 28:06Persistence
- 28:48Development environment
- 29:23Next steps
- 30:08Book
related talks
38mMicroservices, a bittersweet symphony
48mChallenges in Implementing MicroServices
57mEmbracing Microservices
54mThe Long Sad History of Microservices
44mMicroservices, Where Did It All Go Wrong
26mPros/Cons of Microservices
23mLightning Talk: Rethinking Microservices
23mWhy You Had a Bad Time With Microservices