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. Read More
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.
In this episode, we get back to a requirements based topic, and an area that will significantly impact the design of our resulting solution architecture. That topic is security! It's one of the hot topics that organisations want to discuss when moving to the cloud. So I'm pleased to be joined in this episode by another colleague, Andrew Nathan, who has a wealth of knowledge in the cyber security space.
Joining me in this episode is Thomas Maurer, a Senior Cloud Advocate at Microsoft who engages with the community and customers around the world! Most of the focus so far in Cloud with Chris has been on Public Cloud, so Thomas and I adjust course slightly, and talk about Hybrid Cloud, and the new and upcoming features of the Microsoft Azure platform. Get ready to be introduced to a wide variety of Azure Technologies, and how they may be able to strengthen your on-premises, public cloud or multi-cloud deployments. Let's listen in…
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!
Let's introduce Episode #2! This was a suggestion from the community, so a big thank you to Garth Niblock for this one! Last time we talked about requirements, and cost is one dimension of that - but a very important one. When we move into a cloud world, the technology will change, but the way way that we think about cost changes as well. So this episode will be called ‘Cost Control’. Let's listen in…
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?
In my spare time, I work on a pet project called Theatreers. The aim of this is a microservice based platform focused on Theatre / Musical Theatre (bringing a few of my passion areas together). I've recently re-architected the project to align to a multi-region serverless technology stack.
Scalability is one of the common areas where I have seen common misconceptions, when customers begin building on the platform.