Rack-AMQP: Ditch HTTP Inside SOA!

on YouTube ↗22m

" summary

Rack-AMQP maps HTTP semantics onto AMQP so Rack and Rails apps run over a message broker instead of TCP per-request, using Jackalope as the AMQP webserver, AMQParty/Bunny client libraries, and RabbitMQ as the broker. The claimed benefit is persistent connections and built-in pub/sub; a benchmark of 500 requests shows 2.9s vs 3.6s (AMQP faster), the system is in beta and is reported to work in production at Optoro.

AI-written summary · about

" chapters (15)

1. 0:00Start
2. 1:56SOA IS COMPLEX
3. 2:48WHAT IS SOA, REALLY?
4. 3:02COMMUNICATION
5. 4:02TRANSPORT
6. 7:01AMQP MESSAGES
7. 7:11CONVENTIONS
8. 7:36AMQP-HTTP SPEC
9. 10:10RACK API
10. 10:43HTTP EMULATION
11. 11:11JACKALOPE
12. 12:37ARCHITECTURE
13. 13:12CODE - CLIENT
14. 14:23SAMPLE SOA WITH RAILS
15. 18:45REFERENCES

" related talks

• 30mSome Funny Things Happened on The Way to A Service EcosystemChris Hoffman · RailsConf 2018
• 27mRuby Messaging PatternsGerred Dillon · Rocky Mountain Ruby 2011
• 18mRuby Messaging PatternsGerred Dillon · Madison Ruby 2011
• 37mRuby on Rack: The Magic Between Request and ResponseMeagan Waller · RubyConf 2023
• 28mRack for web developersMichael J. I. Jackson · MountainWest RubyConf 2010
• 41mForget about HTTPIrina Scurtu · .NET Summit 2020 Online Conference
• 36mDRb vs. RabbitMQ ShowdownDavy Stevenson · RubyConf 2012
• 28mIn a World of Middleware, Who Needs Monolithic ApplicationsJon Crosby · MountainWest RubyConf 2009