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.
Watch on YouTube
Listen to the Audio
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.
Want to focus on scaling an application, or care about resilience? Have a multi-tenant app, but some of your customers have specific requirements for their scenario? Want to have an application deployed globally, but users housed in a particular area for Data Sovereignty? Then listen in to this session where Chris Reddington is joined by John Downs, talking about The Deployment Stamps Pattern. This is another episode in the series of Architecting for the Cloud, one pattern at a time.
Let’s introduce the next episode -We have another guest! We’re starting to bring a few of those previous topics together in this episode. We touch upon requirements, DevOps, and building applications - or rather APIs - in the cloud. In this episode, I talk with a colleague and friend, Peter Piper, on factors that relate and impact API design. So, without further ado… here we go!
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.