dotnet York

This event will be a two talks on Azure Related Subjects with Rik Hepworth
⚠️ This will be an in-person event, the venue is TBA.
📌 TBA

***

Agenda
🍕 Pizza / Drinks / Networking (18:00 - 18:30)
🗣 Introduction (18:30)
👉 Azure Architecture: Choosing wisely
👉 It's a trap! Stuff a developer needs to know about Azure networking
🍻 Social @ Pub (after the talk)

***

👉 Azure Architecture: Choosing wisely
The menu of Azure services is rich and vast. Selecting the best match for your application’s needs can be a daunting choice.
In this session we will create an architecture for a cloud-native application, with requirements that are taken from several real-world projects to provide a realistic scenario that should resonate with your own experiences.
We will look at the requirements and discuss which Azure services could be used to deliver them, discussing the options and explaining the final choice.
As our architecture diagram steadily expands we will discuss the impact of specific security requirements and how the architecture may need to change to satisfy them. We will also discuss monitoring and telemetry and how they affect our design.
Building an application in the cloud is a team sport. This session should provide learning for all involved: Developers writing applications who are involved in technology choices, IT Pros and Ops teams that manage and operate Azure within their organisation, Architects that design cloud applications and need to go through this process themselves, and finally managers who want to understand more about what their teams need to do in order to build cloud-native applications.

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