Download to read offline
Uploaded byOleg Chorny
Gameaways
Dmytro IELKIN presented on developing a distributed Azure application alone. He discussed starting with a simple ASP.NET MVC website and database, using Azure Web Jobs for background tasks triggered by queues, implementing real-time notifications with SignalR and web sockets, scaling the website and SignalR with auto-scale, scaling out, CDN, and traffic manager, using deployment slots for deployment and database migration, and analytics with Application Insights for page views, exceptions, and custom event tracking. He concluded by encouraging the audience to visit azure.microsoft.com to get started.
![[DO16] Mesosphere : Microservices meet Fast Data on Azure](https://cdn.slidesharecdn.com/ss_thumbnails/do16-170616021542-thumbnail.jpg?width=640&height=640&fit=bounds)
Gameaways
- 1. Пахал Гаврила спозаранку, Гаврилаплуг свой обожал Gameaways.com: История разработки распределенного Azure приложения в одиночку Дмитрий Елькин SDET, Edgar Online
- 2. About me Dmytro IELKIN SDET,Ciklum ASP.NET & Azure
- 3. Agenda Websites BackgroundTasks Real-time interaction Data and Storage Scaling and Performance Deployment Analytics
- 4.
- 5. Start with simplewebsite ASP.NET MVC Database Content
- 6. Background tasks Azure WebJobs Queue Trigger
- 7.
- 8. Scaling and Performance Websiteauto-scale SignalR scalseout CDN Traffic manager
- 9.
- 10. Analytics Application Insights Page viewtracking Exception Tracking Custom Event Tracking
- 11.
Editor's Notes
- #3 Slide Objectives: Explain application is made up by application code and infrastructure code. Speaker Notes: Let’s start with something that you know inside-and-out: your application code. [click] Then, for whatever reason, you decide to deploy your application to Azure. [click] What you do is to allocate a bunch of related resources out of the humongous resource pool provided by Azure, deploy your application code to these resources, and you have a running service. [click] For DevOps’ perspective, you need a way to reliable capture and apply your requirements on resources, which can be referred as infrastructure code.
- #4 Slide Objectives: Explain the agenda of the session. Speaker Notes: Explain this presentation is a high-level overview, so not everything is covered in-depth.
- #5 Slide Objectives: Explain how Azure helps developers to refocus on their applications. Speaker Notes: Before we discuss about specifics, let’s refocus on what you care about – your application/service. Azure is taking a application-centric approach and brings tools and services to support DevOps scenarios.
- #6 Slide Objectives: Explain application is made up by application code and infrastructure code. Speaker Notes: Let’s start with something that you know inside-and-out: your application code. [click] Then, for whatever reason, you decide to deploy your application to Azure. [click] What you do is to allocate a bunch of related resources out of the humongous resource pool provided by Azure, deploy your application code to these resources, and you have a running service. [click] For DevOps’ perspective, you need a way to reliable capture and apply your requirements on resources, which can be referred as infrastructure code.
- #7 Slide Objectives: Explain application is made up by application code and infrastructure code. Speaker Notes: Let’s start with something that you know inside-and-out: your application code. [click] Then, for whatever reason, you decide to deploy your application to Azure. [click] What you do is to allocate a bunch of related resources out of the humongous resource pool provided by Azure, deploy your application code to these resources, and you have a running service. [click] For DevOps’ perspective, you need a way to reliable capture and apply your requirements on resources, which can be referred as infrastructure code.
- #8 Slide Objectives: Explain application is made up by application code and infrastructure code. Speaker Notes: Let’s start with something that you know inside-and-out: your application code. [click] Then, for whatever reason, you decide to deploy your application to Azure. [click] What you do is to allocate a bunch of related resources out of the humongous resource pool provided by Azure, deploy your application code to these resources, and you have a running service. [click] For DevOps’ perspective, you need a way to reliable capture and apply your requirements on resources, which can be referred as infrastructure code.
- #9 Slide Objectives: Explain application is made up by application code and infrastructure code. Speaker Notes: Let’s start with something that you know inside-and-out: your application code. [click] Then, for whatever reason, you decide to deploy your application to Azure. [click] What you do is to allocate a bunch of related resources out of the humongous resource pool provided by Azure, deploy your application code to these resources, and you have a running service. [click] For DevOps’ perspective, you need a way to reliable capture and apply your requirements on resources, which can be referred as infrastructure code.
- #10 Slide Objectives: Explain application is made up by application code and infrastructure code. Speaker Notes: Let’s start with something that you know inside-and-out: your application code. [click] Then, for whatever reason, you decide to deploy your application to Azure. [click] What you do is to allocate a bunch of related resources out of the humongous resource pool provided by Azure, deploy your application code to these resources, and you have a running service. [click] For DevOps’ perspective, you need a way to reliable capture and apply your requirements on resources, which can be referred as infrastructure code.
- #11 Slide Objectives: Explain application is made up by application code and infrastructure code. Speaker Notes: Let’s start with something that you know inside-and-out: your application code. [click] Then, for whatever reason, you decide to deploy your application to Azure. [click] What you do is to allocate a bunch of related resources out of the humongous resource pool provided by Azure, deploy your application code to these resources, and you have a running service. [click] For DevOps’ perspective, you need a way to reliable capture and apply your requirements on resources, which can be referred as infrastructure code.