Unleash Opportunities With Compute options on Azure
Welcome!
HOW DO I ASK A QUESTION?
- If you have a technical or content-related question, please use the Q&A window
- We will address the questions as they come in
CAN I VIEW THIS PRESENTATION AFTER THE WEBINAR?
- There will not be a recording of the session, slides will be shared in the GitHub repository
- Due to the PII we are not keeping the recording of the session
Agenda!
- Why Application Innovation is important?
- Decision Matrix for the compute options on Azure
- Overview of each compute services and recent updates
- Why you need to design differently on the cloud
- Reference Architecture
- Demo on Event Driven Scaling ( AKS + Azure functions)
- Kahoot Quiz
Traditional application has a set of challenges
Aging infrastructure
- Aging hardware, operating systems, and business applications in the datacenter can impact:
- Operational costs, effciency, and reliability.
- Capital expenditure requirements.
- Security, audit and reulatory compliance.
lack of agility
- Deployment time of new services
- Operation is time (and budget) consuming.
- Innovation is happening outside IT inside business areas.
Legacy applications
- Longer release cycles, monolithic and highly coupled architecture.
- Highly IT dependent
- Low application performance and time to market compromise business agility.
The (application) Journey to the Cloud
Azure Cloud Adoption Framework
Cloud app continuum
Lift and Shift (Rehost)
| When to consider
Benefits
Core technologies
Source: Decision Point for Choosing a Cloud Application Migration Strategy, Gartner. Published: 29 March 2016 |
Refactor
| When to consider
Benefits
Core technologies
Source: Decision Point for Choosing a Cloud Application Migration Strategy, Gartner. Published: 29 March 2016 |
Rebuild
| When to consider
Benefits
Core technologies
Source: Decision Point for Choosing a Cloud Application Migration Strategy, Gartner. Published: 29 March 2016 |
Choosing Migration strategy and technology
| Objectives | Cloud strategy | Options to consider | ||||||
|---|---|---|---|---|---|---|---|---|
| Rehost | Refactor | Rearchitect | Re-build | Replace | ||||
| Innovation | 1 | Deliver new capabilities faster | V | PaaS, Serverless | ||||
| 2 | Provide multichannel access, including mobil | V | V | PaaS, Serverless | ||||
| 3 | Enable business agility with continuous innovation | V | V | PaaS, Containers | ||||
| Differentiation | 1 | More easily integrate with other web and cloud apps | V | V | PaaS, Serverless | |||
| 2 | Infuse intelligence into processes leveraging existing investments | V | V | PaaS, Serverless | ||||
| 3 | Increase agility & support scalability requirements of existing applications more cost effectively | V | V | PaaS, Containers | ||||
| Record | 1 | Free up data center space quickly | V | V | VMs, SaaS | |||
| 2 | Reduce capital expenditure of existing applications | V | V | VMs, SaaS | ||||
| 3 | Achieve rapid time to cloud | V | VMs | |||||
Note: Some of the objective might apply to more than one category of applications
What is Cloud Native App Development?
|
Deploy as microservices |
Manage app withDevOpsprocesses & tools |
By 2020, 35% of production apps will be cloud native
Source: IDC FutureScape: Worldwide Developer and DevOps2019 Predictions, Oct 2018
Common cloud native scenarios
|
|
|
|
| Modernize business critical applications | SaaS delivery | Real-time telemetry | Geo-distributed applications |
Key Components of Cloud Native
| Resources | Description | |
|---|---|---|
| Containers | Tool to package your app, run it portably on different hosts in a consistent way. | |
| Serverless | Platform for running and scaling apps where almost all of the operations tasks are managed by the cloud provider. Optimized to let developers focus on code and business value. | |
| Kubernetes | Platform to manage and scale your app reliably (made up of containers) that may span many physical and virtual machines. A tool for operations, noet development. |