[🏫 In-Person] Azure networking and When good services go bad with Rik Hepworth
Details
This event will be a double talk on Stuff a developer needs to know about Azure networking and When good services go bad with Rik Hepworth
⚠️ This will be an in-person event, the venue is Goodlords Offices at Ratoon, 33-35 Fargate, Sheffield.
- 📌 Google Maps: https://maps.app.goo.gl/7BigFQzWAbBXbRUW6
- 🚗 Parking: The APCOA car park on Eyre Street is a five-minute walk.
Agenda:
- 🍕 Pizza/Drinks (18:15 - 18:30)
- 🗣 Introduction (18:30)
- 👉 Stuff a developer needs to know about Azure networking
- 👉 When good services go bad: An Azure murder mystery
- 🍻 Social @ Pub (after the talk)
👉 It's a trap! Stuff a developer needs to know about Azure networking
Cloud was supposed to save us, but those dastardly networks followed us there! So many projects in the cloud now demand that we keep our traffic within the corporate network. But what does that mean for our applications, and how much do we need to understand as developers? Can’t we just leave it to the networking team?
Let’s run through the fundamentals: stuff like DNS and address spaces, that are easy to mess up if you’re not paying attention. Let’s examine what’s meant by ‘hub and spoke’ or ‘split horizon DNS’. This isn’t a session for network professionals who already build and operate corporate systems at scale; this is a session for the developers who need to make sure their applications are going to work, who may not have spent years configuring switches and managing infrastructure, and who just need to know enough to get the job done and avoid the potholes on the journey.
👉 When good services go bad: An Azure murder mystery
In August '24, just after our service went live, something went wrong and we effectively DDOS'd our Azure KeyVault instance for several hours, which really wasn't helpful.
In this session we'll walk through the incident and our journey from being alerted and the initial panic, through collaborative firefighting, to methodical investigation and finally resolution. On the way we'll talk about the importance of telemetry, teamwork, and not placing too much trust in your service provider.
In the end the issue was resolved. Our team learned a lot that day about how we handle incidents and learn from what happened. I hope you'll leave the session thinking about how your team can take what happened to us and make sure you can handle your own incidents effectively.