- PDF Free Download

Size: px

Start display at page:

Download ""

Merilyn Day
5 years ago
Views:

3 Agenda Why use the cloud to build apps? Virtual machines for lift-shift scenarios Microservices and Azure Service Fabric Data services in Azure DevOps solutions

5 Compute Compute Compute Compute Inactivity Period t On and off t Growing fast t Unpredictable bursting t Predictable bursting

20-30% Save 60-80% S M T W T F S J F M A M J J A S O N D Your application portfolio what does it

6 Individual application Dev/test environment in the cloud Application portfolio All dev/test and production environments in the cloud Capacity needed (max+20%) Capacity needed (max+20%) Save 20-30% Save 60-80% S M T W T F S J F M A M J J A S O N D Your application portfolio what does it look like? On and off (30%) Growing fast (15%) Unpredictable bursting (25%) Pred. bursting (20%) 24x7 steady

7 Virtualization there must be more..? It s cheaper isn t it..? My DC is constrained..! My Business Groups are using it..! Public Cloud Platforms SaaS (Software as a Service) Can we STOP doing some things?? Physical Virtual Your Data Center

8 SAAS SOLUTIONS Microsoft Dynamics ENTERPRISE MOBILITY Microsoft Enterprise Mobility + Security Microsoft Azure DEVELOPER + APP PLATFORM Visual Studio Family + Azure App Service DATA + ANALYTICS Cortana Analytics Suite INTERNET OF THINGS Azure IoT Suite CLOUD INFRASTRUCTURE Azure + Azure Stack + Operations Management Suite

10 Microsoft SQL Server VM Microsoft SQL Server VM Lift and Shift Microsoft Azure Corporate Network Application VM Application VM Storage Archive key data inexpensively PDF DOCX JPG VIDEO DB

11 Key Scenarios to get started with Azure On-premises / Hosting Services IIS/SQL Server Based Web Apps Microsoft SQL Server IIS MySql Non-IIS Open Source Web Apps Microsoft Azure Web Apps - Take your web apps to the cloud using inexpensive App Service Web Apps

12 Check-in Key Scenarios to get started with Azure Full Dev/Test environments Production Build Staging Master branch Visual Studio Team Services GIT / TFS Test branch Dev/Test Developers

operate a service at scale Plan Monitor +

14 Why a microservices approach? Continually evolving applications Faster delivery of features and capabilities to respond to customer expectations Build and operate a service at scale Plan Monitor + Learn 1 4 Development Production 2 Develop + Test 3 Release

Microservices application approach A microservice application separates functionality into separate smaller services.

15 Monolithic application approach A monolith app contains domain specific functionality and is normally divided by functional layers such as web, business and data Scales by cloning the app on multiple servers/vms/containers App 1 Microservices application approach A microservice application separates functionality into separate smaller services. App 1 App 2 Scales out by deploying each service independently creating instances of these services across servers/vms/containers

State in Monolithic approach Single monolithic database Tiers of specific technologies State in Microservices approach Graph of interconnected microservices State typically scoped to

16 State in Monolithic approach Single monolithic database Tiers of specific technologies State in Microservices approach Graph of interconnected microservices State typically scoped to the microservice Variety of technologies used Remote Storage for cold data stateless presentation services stateless services with separate stores stateless services stateful services

17 Azure Service Fabric A platform for reliable, hyperscale, microservice-based applications Microservices High Availability Simple programming models Hybrid Operations Hyper-Scale High Density Data Partitioning Rolling Upgrades Automated Rollback Service Fabric Low Latency Stateful Services Placement Constraints Health Monitoring Fast Startup & Shutdown Code Orchestration & Lifecycle Management Self-healing Replication & Failover Resource Management Azure Private cloud Other clouds

Fabric (Stateless, stateful or Actor services) 1 role instance per VM Uneven

failure recovery Limited fault tolerance Many microservices per VM Even

18 Azure Cloud Services vs. Azure Service Fabric Azure Cloud Services (Web and Worker Roles) Azure Service Fabric (Stateless, stateful or Actor services) 1 role instance per VM Uneven utilization Low density Slow deployment & upgrade (bound to VM) Slow scaling and failure recovery Limited fault tolerance Many microservices per VM Even Utilization (by default, customizable) High density (customizable) Fast deployment & upgrade Fast scaling of independent microservices Tunable fast fault tolerance

20 transactional processing fully managed, scalable, queryable, schemafree JSON document database service for modern applications rich query managed as a service elastic scale schema-free data model internet accessible http/rest arbitrary data formats

22 SQL IaaS Run any SQL product on cloud VM Support for SQL Server, Oracle, MySql Ready to go VM images available in Gallery Persistent storage using attached disk in blob storage Has all the benefits and powers of VMs combined with the full features of a SQL Engine

23 Azure Data Warehouse A relational data warehouse-as-a-service Power BI Hadoop App Service Azure SQL Database Azure SQL Data Warehouse Intelligent App Azure Machine Learning

25 What is DevOps? Development and Operations collaboration

27 The DevOps conversation PEOPLE Collaborate more Share common goals Focus on improvement BRINGING PEOPLE TOGETHER PROCESS Eliminate waste Increase efficiency Streamline feedback DELIVERING VALUE FASTER TOOLS Enhance productivity Enable collaboration Facilitate experimentation EXECUTING A DEVOPS STRATEGY

28 DevOps habits and practices PRACTICES Automated Testing Continuous Integration Continuous Deployment Release Management PRACTICES Usage Monitoring Telemetry Collection Testing in Production Stakeholder Feedback PRACTICES Code Reviews Automated Testing Continuous Measurement PRACTICES Application Performance Management Infrastructure as Code Continuous Deployment Release Management Configuration Management Automated Recovery FLOW OF CUSTOMER VALUE TEAM AUTONOMY & ENTERPRISE ALIGNMENT BACKLOG refined with LEARNING EVIDENCE gathered in PRODUCTION MANAGED TECHNICAL DEBT PRODUCTION FIRST MINDSET INFRASTRUCTURE is a FLEXIBLE RESOURCE PRACTICES Enterprise Agile Continuous Integration Continuous Deployment Release Management PRACTICES Testing in Production Usage Monitoring User Telemetry Stakeholder feedback Feature flags PRACTICES Application Performance Management Infrastructure as Code Continuous Delivery Release Management Configuration Management Automated Recovery

30 Strong IT performance is a competitive advantage Firms with high-performing IT organizations were 2x as likely to exceed their profitability, market share, and productivity goals Deploy code 30x faster and with 200x shorter lead time when compared to lower-performing peers DevOps practices improve IT performance Have 60x fewer failures and recover from failure 168X faster when compared to lower-performing peers

31 The DevOps cycle 5. Deploy to Cloud 2) Code Repository 3) Build 4) Test Contoso App 1. Developers Azure 6. Monitor and Improve

32 Monitor & Learn Develop Build & Test Deploy DevOps in the Microsoft ecosystem Developer Workstation Build/CI Release Monitor Team Collaboration Test TFS DEV TEST QA Workstations - On-Premises Hybrid Cloud Services - On-Premises Hybrid Cloud Environments - On-Premises Hybrid Cloud Monitoring - On-Premises Hybrid Cloud

Visual Studio Everywhere. Build Great Cloud Apps

Visual Studio Everywhere. Build Great Cloud Apps Visual Studio Everywhere Build Great Cloud Apps Agenda Why use the cloud to build apps? An overview of Microsoft Azure Virtual machines for lift-shift scenarios Microservices and Azure Service Fabric Data