RabbitMQ: Patterns for Applications
This book is 100% complete
Completed on 2015-07-04
About the Book
It’s exciting – that new tool smell… and there are promises of dramatic improvement in performance, architecture and finally getting rid of that stain on your favorite rug! Ok, maybe RabbitMQ won’t clean your rug for you, but it is incredibly fast and it can improve your architecture!
There’s a small problem, though. Learning new technologies can be hard. And time consuming. And frustrating, if you’re doing it on your own. I’ve been there. You’ve been there. Countless people have tried to pick up a new tool and banged their head in to a wall, hard. It’s unfortunate but it’s often the reality that we live and work in.
Learning New Terms, New Patterns
RabbitMQ isn’t terribly complex, but it does have a fair number of new and potentially confusing concepts to learn. On top of the concepts, you also have good patterns that should be followed. So, how do you learn these patterns as well as these concepts? Where can you go to find the best way to approach application development, with RabbitMQ? What patterns should be used when, and ignored at other times?
It can be hard to learn this on your own. Fortunately, you don’t have to face the pitfalls of learning RabbitMQ’s patterns alone!
With the RabbitMQ: Patterns For Applications ebook, you will get 9+ chapters of content covering the patterns and practices that you need to effectively work with RabbitMQ.
More than a decade after it's release, the "Enterprise Integration Patterns" book is still the source of material for messaging patterns. For myself, and countless others that have read and referenced the myriad of patterns in these pages, application design will never be the same. Message based architecture has brought me out of the dark ages of hard code and deeply nested structures with a new world of asynchronous communication and decoupled applications.
The Patterns of RabbitMQ
Systems such as RabbitMQ have taken the patterns and practices outlined in this book and other well known messaging solutions, and built them in to the software directly. For example, you no longer need a separate message broker and queue. You don't have to manually implement pub/sub or routing slips. You need not worry about the implementation details of so many patterns found in this book.
Yes, it is important to understand many of these patterns and how they apply to your application development. But so many of them are built in, and you only need to know the specifics of how to use these patterns with RabbitMQ. That's where this email course comes in - a guide to work your way through some of the most common and useful messaging patterns, applied to application development with RabbitMQ.
About This Book
The original content of this book was created for a 9-day email course titled RabbitMQ: Patterns For Applications. This book is a copy & paste of the same content, delivered in the same order, to give you a collected works edition. If you would prefer not to pay for the ebook, you can get the same content delivered to your inbox, 1 day at a time, though that email course.
As you read this book, keep in mind that each of these short chapters was originally an email with each email sent 1 day apart. As such, you'll see references to "tomorrow's email" and "coming up tomorrow", etc.
The content of both the email course and this book cover common messaging patterns applied to application design with messaging in RabbitMQ. When you're done with this book, you'll have the knowledge you need to get up and running quickly and effectively. Your applications and architectures will have a head start on the path of working with asynchronous, long-running processes to create robust and fault tolerant systems.
- The Patterns of RabbitMQ
- What To Expect
- How This Book Is Written
- Coming Up
How RabbitMQ Saved My SaaS
- A Series Of Unfortunate Events
- Except “Stable” Was More Like “Frozen In Time”
- Catching Up As If It Were Never Down
- Do You See The Trend?
- Learn The Patterns That Will Make It Easier
Pattern 1: Don’t “sendToQueue”, Publish!
- Broker? Queue? What?
- What Kind Of Intelligence?
- Send To Queue Is An Anti-Pattern (Mostly)
- An Ever-Changing Landscape
- What Kind Of Data?
Pattern 2: Send A Complete Document, Or Just An ID?
- One Of Many Good Patterns
- Sending A Complete Doc vs An ID
- Just Documents?
Pattern 3: What Kind Of Messages Should I Send?
- Context And Meta-Data
- Patterns Of Message Types
- Event Messages
- Command Messages
- Request Messages
- Coming Up, The Archetypes In Depth
Pattern 4: Event Messages with Pub/Sub
- Event Names
- Publish/Subscribe For Event Messages
- Exchange Per Event Type
- Missed Messages and Time To Live
- From Past To Present
Pattern 5: Command Messages with Point-to-Point
- Command Names
- Point-to-Point For Commands
- Exchange Per Object
- Once, and Only Once!
- Sometimes A Command Needs A Response
Pattern 6: Request/Response with Reply-To and Correlation ID
- Request Names and Channels
- Correlation ID and Reply-To Queues
- A Do-It-Yourself Pattern, And sendToQueue
- Commands w/ Responses, and Separating Requests
- Handling Request Timeouts
- What About Exceptionally Long Running Processes?
Pattern 7: Status Updates with Asynchronous Response
- Combining Commands with Events
- Events And Updates Without Reply-To
- Correlation ID And Reconstructing State
- Command Query Separation, Revisited
- What If I Can’t Recover Or Process That Message?
Pattern 8: Handling Bad Messages with Dead Letter Exchanges
- Dead Letter Exchanges
- Rejecting Or Nacking A Message
- TTL and Max Queue Length
- Ok, It’s Dead. Now What?
- Many Options For Dead Letters
- Great! Where Can I Learn More?
Appendix A: Additional Resources
- RabbitMQ For Developers
- RabbitMQ Tutorials And Documentation
- RabbitMQ In Action
- RabbitMQ In Depth
- Enterprise Integration Patterns
- The RabbitMQ Community
- … And So Much More
About Derick Bailey
- Thanks For Reading
The Leanpub 45-day 100% Happiness Guarantee
Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms...