One Microservice is No Microservice - They Come in Systems

on YouTube ↗37m

" summary

Claim: microservices only make sense as distributed systems and synchronous REST chaining fails for performance and team complexity. Uses Akka, Play and SBT with Lagom as an opinionated layer, Cassandra for persistence, and CQRS/event sourcing so state is stored as events. The demo environment boots many services locally with runAll local dev environment, exposes a service API for intra-service calls, and relies on a persistence API with event sourcing; it’s usable but still a technical preview.

AI-written summary · about

" chapters (10)

1. 0:00Start
2. 13:45ARCHITECTURE PRINCIPLES
3. 17:55SOFTWARE DESIGN PATTERNS
4. 24:12SCALA, AKKA AND PLAY ARE GREAT FITS HERE
5. 27:43WHAT IS IN LAGOM?
6. 28:44HIGHLY OPPINIONATED
7. 31:00LAGOM PERSISTENCE API
8. 32:31DEVELOPMENT ENVIRONMENT
9. 33:05NEXT STEPS FOR LAGOM
10. 34:57CONTRIBUTE TO LAGOM

" related talks

• 23mWhy You Had a Bad Time With MicroservicesEthan Garofolo · EmpireJS 2018
• 38mMonolith vs. MicroservicesRafa Paradela · Scala Days 2023 Seattle
• 49mChallenges in Implementing MicroservicesFred George · GOTO Amsterdam 2015
• 43mGo micro with MicroservicesMariusz Gil · International PHP Conference Spring 2017
• 44mMicroservices, Where Did It All Go WrongIan Cooper · GOTO Copenhagen 2024
• 54mThe Long Sad History of MicroservicesGreg Young · Build Stuff 2016
• 45mMicroservices: A retrospectiveTomer Gabel · Øredev 2019
• 48mChallenges in Implementing MicroServicesFred George · Agile Singapore Conference 2016