Ever wondered how complex integration systems / enterprise messaging works? Curious about whether there’s a way to bypass and prioritise certain messages? Then join this episode as Chris Reddington and Will Eastbury explore the Priority Queue and Pipes and Filter patterns. Spoiler - These aren’t new cloud design patterns, and are well known patterns in the messaging world!
Watch on YouTube
Listen to the Audio
Related
Do you have an application with some specific requirements around scalability, and continuity of service? What happens if your service is hit by heavy load? Could performance/reliability issues cause an impact to your solution? This is where both the queue-based load levelling and competing consumers patterns shine. Tune in and listen to Chris speak with Will Eastbury as they discuss both of these patterns. This is another episode in the series of Architecting for the Cloud, one pattern at a time.
Episode
You’ve heard Peter and Chris talk about The Façade pattern previously. These patterns build upon the Façade concept. The façade layer could be used to translate requests between various subsystems, aggregate multiple backend requests into a single response and offload specialised functionality to a gateway proxy. Tune in and listen to Peter Piper join Chris Reddington, as they discuss The Anti-corruption layer, Gateway Aggregation and Gateway Routing patterns! This is another episode in the series of Architecting for the Cloud, one pattern at a time.
Episode
You may have joined Peter and Chris in some of their previous episodes such as the API Economy, The Backends for Frontends & Strangler Pattern, or The Anti-Corruption Layer, Gateway Aggregation and Gateway Routing patterns. They’ll will be continuing our journey talking about API Cloud Design Patterns, as they talk about the Gatekeeper and Valet Key Patterns in this episode of Cloud with Chris. This is another episode in the series of Architecting for the Cloud, one pattern at a time.
Episode
The event sourcing pattern is a well-known pattern and has been around for some time. The idea is that you use an append-only store to record the full series of actions taken on the data. This combines well with the materialized view pattern, where a pre-populated view is generated over one (or more) data stores when the data isn’t in an ideal format for querying. These two patterns are common patterns used in an event-driven architecture. Join Chris and Steph as they talk about both of these patterns and how they may be able to help. This is another episode in the series of Architecting for the Cloud, one pattern at a time.
Episode