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.
Watch on YouTube
Listen to the Audio
You may have heard of patterns like the retry pattern, circuit breaker, CQRS or bulkhead. But have you heard about the Geode pattern? Join Chris and Will Eastbury in this session as they talk through how this pattern can help improve latency and increase availability for your application.
How are you thinking about handling load on your application, scaling out perhaps? But what about if you’re building a multi-tenant service and worried about safeguarding resources on a per tenant basis? What happens if there’s a temporary blip, and there are issues that impact the stability of the application? Then tune in to this episode where Chris is joined by John Downs, talking about the Throttling, Retry and Circuit Breaker Patterns. This is another episode in the series of Architecting for the Cloud, one pattern at a time.
Developing applications for new platforms, and struggling to manage your API estate? Finding you have to refactor, or in a scenario where your code isn’t clean? Want to decouple your backend APIs from your clients, and figure out how you can move from a legacy set of APIs to modern APIs? Then tune in and listen to Peter Piper join Chris Reddington, as they discuss the Backend for Frontends and Strangler Pattern, with an honourable mention to the Façade pattern as well! This is another episode in the series of Architecting for the Cloud, one pattern at a time.
Starting to think about the data layer of your application, and concerned about scalability of your solution? Or have some form of application that needs to have segragation of data, perhaps customers with requirements to have their data in a particular geography? Then the first part of the session may be for you, focused on the Sharding pattern! But what about if you’re using a data store which doesn’t support secondary indexes? Won’t you be limited on the efficiency and types of queries that you can run across your data? Then this is where you may be interested in the Index Table Pattern. Listen in to this session where Chris Reddington is joined by Steph Martin, talking about both of these patterns. This is another episode in the series of Architecting for the Cloud, one pattern at a time.