Forget about HTTP
summary
Claim: synchronous HTTP calls become brittle for inter-service data and lose requests; demos show an HTTP client fires ~3,501 requests in 20s that the API never processes, gRPC (proto contracts) removes code coupling, RPC via a broker preserves requests, and full messaging pumps 38,000 messages in 20s using RabbitMQ + AMQP. Tools and patterns shown: .NET Core 3, Polly for retries, gRPC, RabbitMQ, MassTransit, Kafka, Azure Service Bus (AMQP), queues/topics/fanout routing. Built demos prove messaging keeps requests when consumers are down and switching to AMQP can yield ~4x throughput gains.
AI-written summary · about
chapters (17)
- 0:00Start
- 3:11Scaling the MONOLITH
- 4:34MICROSERVICE
- 10:44It's perfectly fine to use async HTTP Calls
- 12:15HTTP General Notes
- 13:34Challenges
- 28:54Solutions to eventual problems
- 29:35Agility
- 30:58Scalability
- 34:07Queues
- 34:53Actor model
- 35:24Reactive Manifesto
- 36:31Message Brokers
- 38:01AMQP General Notes
- 39:45Direct exchange routing
- 40:31Fanout exchange routing
- 40:56Topic Exchange
related talks
41mForget about HTTP
49mCommunication in a microservice architecture
33m"RPC frameworks overview"
34mCall me maybe - communication between microservices
01h 09mBuild a Highly Performant Interservice Communication with gRPC for ASP NET Core
01h 01mThe Unsung Hero of Modern Software: Asynchronous Messaging
56mDistributed Messaging patterns
31mRPC Frameworks Overview