Rethinking REST in a Microservices World
summary
Claim: replacing synchronous REST calls with asynchronous messaging prevents failures from bubbling through a microservice mesh. Uses Lightbend Lagom with Cassandra, Akka Streams and a demo "chirper" app where like counts are pushed via an event stream (events carry UUID offsets) and consumed with at-least-once messaging; an actor + back‑off supervisor and cluster singleton ensure one consumer and automatic restarts. Websockets deliver eventual consistency (a few seconds delay), JWTs let clients carry auth to avoid extra sync calls.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:03Asynchronous IO concepts
- 4:00Synchronous vs. asynchronous
- 6:39Benefits of async systems
- 10:35Consistency and isolation
- 12:44REST and microservices
- 14:42Monolith to microservices
- 17:49Architectural strategies
- 21:16Implementing async patterns
- 23:26Lagom framework demo
- 39:39Client-side communication
- 47:41Q&A and conclusion
related talks
01h 22mreactive James Roper 4 21 16
11mLightning Talk: Event Based Communication in Complex Micro-service...
37mBeyond Microservices: Streams, State & Scalability
01h 01mThe Unsung Hero of Modern Software: Asynchronous Messaging
42mLightbend Lagom: Microservices Just Right
48mIntegration- and conversation-patterns for microservices
28mPractical Microservices, Practical Whiskey
37mOne Microservice is No Microservice - They Come in Systems