When building solutions in the cloud, security is often a pillar that we hear come up in the requirements discussion. But how does that translate into the real world? Particularly defending against DDOS attacks? Check out this episode, where Cam Adams joins Chris and talks about some of the recent work that he has been doing, helping customers defend against this.
Watch on YouTube
Listen to the Audio
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.
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…
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!