Taking The Hippie Bus To The Enterprise
summary
A lightweight .NET messaging library called Rebus (≈3,700 C# lines, on GitHub and NuGet) is a thin layer over MSMQ (also supports RabbitMQ, Azure Service Bus, SQL transport) that guarantees durable asynchronous delivery via error queues and retries. Three concrete demos show: splitting a monolith with publish/subscribe between front/back office; handling a flaky SOAP credit service that fails ~75% of calls using an integration endpoint and automatic retries; and a stateful process manager using the defer API to set a 10s timeout and resume or compensate — all demos run successfully.
AI-written summary · about
chapters (16)
- 0:00Start
- 2:30Big system size
- 4:41Problem summary
- 4:57The solution: Messaging
- 5:44Messaging via durable, asynchronous queues
- 6:53Windows FTW!!1
- 7:29Meet Rebus
- 8:41"Hippie bus"?
- 9:48Motivation
- 11:24Philosophy
- 24:05st problem System that's becoming too big
- 29:24nd problem
- 35:10rd problem Complex coordination and timing
- 44:17Summary Messaging provides a model that can • help you gue the pieces together when you break down a
- 49:27Litterature
- 49:56Thank you for listening!
related talks
56mDistributed Messaging patterns
01h 01mMessage Brokering and Event Driven Architecture on Azure
55mForget about HTTP
41mForget about HTTP
01h 01mBeyond Pub/Sub - Advanced Messaging Patterns
56mMicroservices from the trenches
50mMiddleware Showdown: Exploring Diverse Messaging Solutions
01h 03mHow to build .NET Microservices