
Messages vs Events and Transport Independence

#187 - The Tao of Microservices - Richard Rodger
Topic 5 of 8
Published Aug 12, 2024 · Clip 28:41–41:19 (12:37)
Richard distinguishes his message concept from event sourcing by defining two axes: synchronous vs asynchronous and consumed vs broadcast, citing Fred George's insurance quoting example. He explains transport independence via gateway plugins translating HTTP and Amazon events into messages, his AI podcast chatbot built on SQS Lambdas, and model-driven architecture—type-safe architecture-as-code (Terraform/Pulumi-style) that maps message patterns to deployment topics, keeping business logic independent of transport. He notes the same pattern applies to RabbitMQ, EventBridge, and Erlang/OTP.