The document discusses the transition from monolithic microservices to micro streams, emphasizing the inevitability of cascading events in distributed systems. It highlights key concepts such as event sourcing and the importance of at-least-once delivery, idempotency, and eventual consistency in serverless architectures. The author, Hugh McKee, advocates for minimizing work during wait periods in microservice interactions.

1. From Monolithic
Microservices to
Micro Streams
Hugh McKee
Developer Advocate

6. RESTful synchronous RPCs

10. Monolithic Microservices

11. Intra service RPCs

12. Whatever can happen,
will happen.
Murphy’s Law

13. Async Cascading Events

16. Micro Streams - Cascading Events

17. With distributed systems
It’s not if something
happens
It’s when something
happens
Hugh’s motto

18. Single Points of Failure

21. Replicated Reference Data

25. The chains of habit are too
weak to be felt until they are
too strong to be broken.
Samuel Johnson

26. Micro Stream Examples

44. Do the least amount
of work when
someone is waiting.

64. Event-sourcing

67. Command
Query
Responsibility
Segregation

71. ● At-least-once-delivery
● Idempotency
● Multi transactional
● Eventual consistency

72. At-least-once-delivery

73. Idempotency

74. Multi transactional

75. Eventual consistency

79. Serverless Microservices
A server-less, database-less, broker-less, ops-less
PaaS - kalix.io

80. From Monolithic
Microservices to
Micro Streams
Hugh McKee
Developer Advocate
@mckeeh3
Thanks!
Q&A