Forget about HTTP

on YouTube ↗41m

" summary

Argues against synchronous HTTP clients between microservices and shows messaging improves throughput and reliability: an RPC-via-broker run hits 5586 messages in 20s vs the lower HTTP run, switching HTTP→AMQP doubling throughput in another test. Demonstrations use RabbitMQ (dead‑letter queues, ack/nack, channels) and mentions MassTransit, Kafka, Azure Service Bus, SQS; cites Amazon (150 internal APIs per page), Netflix (5.5B/day), JP Morgan (1B messages/day) as real-world scale reasons to prefer messaging.

AI-written summary · about

" chapters (9)

1. 0:00Start
2. 0:50MONOLITH
3. 2:52Scaling
4. 4:01MICROSERVICES?
5. 11:16HTTP General Notes
6. 14:31Non-functional requirements
7. 16:57Coupling
8. 30:26Actor model
9. 38:29Fanout exchange routing

" related talks

• 55mForget about HTTPIrina Scurtu · .NET Fest 2019
• 49mCommunication in a microservice architectureIrina Scurtu · Riga Dev Days 2019
• 01h 01mThe Unsung Hero of Modern Software: Asynchronous MessagingIrina Dominte · NDC London 2025
• 50mMiddleware Showdown: Exploring Diverse Messaging SolutionsChris Patterson · NDC London 2024
• 38mStream-style messaging developmentVyacheslav Lapin · JavaDay Kharkiv 2015
• 59mEffective Microservice Communication and Conversation PatternsJimmy Bogard · NDC London 2020
• 01h 03mChoosing the Right Messaging Solution for Your ArchitecturePoornima Nayar · NDC Melbourne 2025
• 48mIntegration- and conversation-patterns for microservicesDirk Fröhner · JCON-ONLINE 2021