Architect your Azure solutions

Video Statistics and Information

Video
Captions Word Cloud
Reddit Comments
Captions
before you can run your Solutions in Azure you need to know what services to deploy in the next several minutes I'm going to show you how to architect your Solutions and identify Azure services that can support your workloads [Music] my name is Eric Boyd I'm an Azure MVP a Microsoft Regional director and the founder of responsivex where we help customers run workloads and develop applications in Azure in my work at responsivex I regularly deliver assessments and architecture design sessions to help customers identify and architect solutions for azure in this video I'm going to share my knowledge from my experiences helping customers architect Solutions in azure before architecting Solutions you need to identify the solutions you want to deploy to azure once you have a solution you need to decompose the solution into its parts and make some decisions on architectural style in the platforms and Technologies you're going to use now there are several approaches for transforming your organization using Azure in addition to being a technologist I'm a business owner and I think the most pragmatic approach is when a catalyst from the organization drives Technology Innovation now this isn't a one-way Street sometimes individuals leading and managing your organizations just aren't aware of certain Innovations and as a result they might not know what's possible this is where you can help your organizations by suggesting ways to reduce cost and deliver more value common drivers that might help you think of Solutions in your organization that could be great candidates for Azure include providing better support for remote work utilizing resources more efficiently reducing costs increasing scale to meet demand to provide great experiences for your users replacing aging on-premises infrastructure that's just fragile and risky and improving compliance and security posture now in my hypothetical case my organization has two workloads that I think are great fits first is our Erp system this workload is very important for my organization but right now it's on very old Hardware on software that's aging or going out of support soon or support has already ended it doesn't perform well there isn't much in the way of redundancy for high availability and the Aging Hardware is causing frequent outages from failures so this is a great candidate to explore because moving to Azure might help us avoid making upfront Hardware purchases my second workload is brand new the sales group wants to create a new customer facing e-commerce solution this is low risk because it's a brand new solution and we have a blank canvas to work with so that we can architect solution fit for purpose you now need to decompose your workloads into the individual components and services that make up the overall solution now the Erp system is easy because we're not going to change the Erp system we just want to upgrade the OS and application servers to current versions and Azure will make it possible for us to increase the size and performance of the servers and infrastructure without buying new hardware since the eCommerce web app is brand new we will have to make some design decisions and architect the application and determine what Azure services to use at the most basic level we know we'll need a compute service to host our web application and we'll need a storage service or multiples to store our data the Azure architecture Center on Microsoft docs is a valuable resource to learn about architecting applications and Solutions on Azure and the information you'll find here is usually just great application architecture guidance and not even dependent on azure within the Azure architecture Center you'll find the application architecture guide you can get there from the architecture menu by clicking on get started or by clicking on the explore Cloud best practices Link in the middle of the screen this section will guide you through a structured approach to designing your applications in Azure one of the first design decisions you'll have to make is the architectural style you will use for your solution now your eCommerce web app might consist of multiple architectural Styles if I were designing a new eCommerce solution that had a fair amount of complexity needed to be able to scale to meet demand had Integrations with other systems like the Erp system for example and was expected to have frequent improvements in new features and I had a team that could develop and support it I'd probably choose a microservices architectural style with services that were designed with event driven and webq worker architectural styles the Azure architecture Center provides a wealth of information and guidance about each of these Concepts to help you make the best decisions for your solution organization team and requirements once you know the type of architecture you are building you can choose the services to use for your solution now you should focus on the largest building blocks first and with that solid foundation you can evolve your solution and make additional technology choices along the way the major building blocks I recommend focusing on first are compute data and messaging with each of these you need to familiarize yourself with the different models and basic features of each service the technology choices section of the Azure architecture Center is a helpful resource for identifying the services that are best suited for your solution the choose a compute service guidance provides an overview of the hosting models and basic features for each compute service you'll also find a decision tree that will help guide you through the decision making process and matrixes of characteristics that will help you narrow in on services that meet your needs for my eCommerce web app I'm going to create microservices organized by business capability I'm planning to develop them with net core some will be request response web apis and some will perform background processing and I'll have front-end web apps that talk to my apis for Simplicity I'm going to choose a combination of azure app service and Azure functions for my compute services if I plan to containerize my microservices I could select Azure kubernetes service and if I had Legacy middleware that I needed to install and configure on a server requiring full control of the OS I could select virtual machines one of the interesting and liberating advantages of using Azure is you can easily select a combination of these Services allowing you to choose the right Azure service for the job like compute the Azure architecture Center has guidance for choosing a data store here you'll find overviews of the various datastore models and the Azure services for each model you'll also find suggestions for the types of data and solutions that are best suited for each data store and like compute you'll also find a decision tree that will help you select the best data store and Azure service for your data for my Ecommerce app I'm going to use a combination of Cosmos DB blob storage and Azure search in the future I expect we'll use Azure synapse or data bricks for Analytics when designing microservices Solutions Solutions designed to scale and solutions with occasionally connected clients you often have a need for messaging Azure has several messaging services you can select from and you'll find guidance in the Azure architecture Center for selecting a messaging service you first need to decide if you have asynchronous or real-time messaging needs and the choose a messaging service guidance provides an overview of each with guidance and service recommendations for my eCommerce app when orders come in I want to publish messages on a message bus that other services can subscribe to and act on so I'm going to use Azure service bus for this requirement these are the core Services I need for my solution there are additional service that I will likely incorporate into my solution like AI services for personalization and recommendations and identity services for letting customers register and log in and you will find similar guidance for these other services in the Azure architecture Center if you are looking for inspiration for your Solutions architecture you can browse reference architectures in the Azure architecture Center here you will find architecture diagrams and overviews of how various Azure Services can be composed together to enable Solutions architecting your Solutions is an essential step towards deploying your workloads into azure before you can architect your Solutions you need to identify what workloads in your organization are good candidates for azure you then need to decompose each workload into a solution architecture and select Azure services to fulfill each component of the architecture there are other factors that you should consider like availability networking monitoring and security because these will likely influence your architectural decisions and as part of your architectural efforts you should also estimate the usage and load of your application so you can estimate the size of your Azure resources in the next video of this series I will show you how to organize your resources in Azure to help you secure manage and track the costs of your Azure environment and before I wrap up I'd like to invite you to join me at our weekly Azure live q a session during the 30-minute session I will host an interactive and live q a to answer your Azure questions [Music] foreign
Info
Channel: Microsoft Azure Developers
Views: 12,523
Rating: undefined out of 5
Keywords: Azure, Functions, Serverless, Computing, azure app service, azure developers, azure dev cli, azure functions
Id: y8Hy0uYL3hg
Channel Id: undefined
Length: 9min 38sec (578 seconds)
Published: Thu May 25 2023
Related Videos
Note
Please note that this website is currently a work in progress! Lots of interesting data and statistics to come.