Path to GA, How-To Guide: A RabbitMQ Story
summary
Project integrates RabbitMQ into Knative Eventing by implementing a Broker + Source model, a sandbox repo, GitHub Actions release wiring, and components like receiver adapter, dispatcher, consumers and DLQ; testing uses unit e2e conformance tests and downstream pipelines; quality gates target 1,000 messages per second and at-least-once delivery; documentation, demos and user feedback shape priorities; avoid building whole system up front, prefer working-group alignment, concrete measurable goals, focused metrics (not logs), and repeatable benchmarks run on each release.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:17What's next
- 1:23Knative Pieces
- 4:32Knative is OSS at the end of the day
- 6:53Where to start?
- 9:06Now, the Integration
- 12:49The "Whole" Picture
- 14:11Eventing RabbitMQ Example
- 16:17RabbitMQ Implementations
- 17:55Define quality Gates for (and from) users
- 20:35Gather valuable metrics
- 23:25Avoid common mistakes
related talks
48mTesting Your Message-Driven Application
16mApache Kafka + MQTT = A Powerpack combination for end-to-end testing
38mTake The Path Of Least Resistance For Your Test Data
15mCapacity planning with Capybara and RabbitMQ
39mAll of those tests you have and none of them cover Message Queues
47mTesting message driven applications with Spring
30mElevating Event-Driven Architecture: Boost your delivery with AsyncAPI and Microcks
15mAn Empty Kafka is a Sad Kafka