15 - The Sharding and Index Table Patterns

15 - The Sharding and Index Table Patterns

2020-11-13

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 segregation 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.

Related Content

14 - The Deployment Stamps Pattern

14 - The Deployment Stamps Pattern

2020-11-06

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.

5 - The API Economy

5 - The API Economy

2020-04-25

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!

1 - Requirements in Context

1 - Requirements in Context

2020-03-01

This is the first episode! We'll be talking about all things requirements. Why is that? Well, that's the place any kind of project should start - What are you aiming for, what are you trying to achieve and what is the context?