Thanks to Ruth Hartnup for the base image! CC BY 2.0
If you’ve been programming for a while, it’s probable that someone, somewhere, has recommended the Gang of Four book.
The book dissects Object Oriented programming. It lists numerous ways of royally messing things up, but it’s claim to fame is that it also lists ways to do it right! These well tested paths to success often come with explanations for when to use them and why they’re good at avoiding common pitfalls.
These are design patterns. They’re embedded in the culture of programming, and they’re an amazing way to learn from others’ mistakes. At the outset of any project, a lot of paths are open to you. Design patterns illuminate the dark paths from the healthy, low stress approaches.
Today, we’re releasing our very own set of best practices and anti-patterns in the form of a white paper. It’s a quick read and will save you time as you tinker on your own workers and message queues. So, what do you have to lose?
Download the latest white paper from Iron.io: Best Practices and Anti-Patterns for Workers and MQs.
Give it a read and let us know what you think!