Most messaging applications are designed in isolation: one instance each of the sending and receiving apps. But can the design provide high availability? Will it scale up? How easy is it to migrate within the network? The best return on your consulting investment is to engage professional services early in the product lifecycle, during the design stage.
The term anti-pattern refers to something that intuitively appears to be beneficial but turns out to be ineffective or even destructive in practice. The problem with anti-patterns is that they tend to be perpetually re-invented under the guise of innovation.
Common examples include systems that:
- Are cheap to build but prohibitively expensive to operate.
- Work well in unit and QA testing but do not scale under stress testing or in production.
- Include dependencies on external factors such as network topology that render the application rigid and brittle.
- Cannot be made highly available due to conflicting design constraints.
- Cannot be properly secured.
- Do not provide adequate monitoring or diagnostics.
Work with messaging systems long enough and you will see a lot of projects attempting to implement anti-patterns. Work as a consultant across many customers and industries and you see many different types of anti-patterns. But just when you think you have seen it all, someone invents a new one.
Don’t be the company that invents the next anti-pattern. Better yet, don’t be the company that re-invents a well known anti-pattern, as so many do.
The veteran consultants at IoPT understand messaging architecture deeply and can tell you when, why and how a design breaks the underlying messaging model. Engage a consultant to validate your design or to provide design services and custom solution architectures tailored to your requirements and budget.
Contact us today to discuss your next messaging project.