...
- 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
|
Refactor
| When to consider
Benefits
Core technologies
|
Rebuild
| When to consider
Benefits
Core technologies
|
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 | |||||
| Info |
|---|
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 |
| Info |
|---|
By 2020, 35% of production apps will be cloud native |
| Info |
|---|
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. |
Azure: The Power Of Choice
Compute
Virtual Machines
- Ubuntu, Red Hat, Windows, SUSE, CoreOS
- DevOps Extensions with Chef and Puppet Multiple sizes
- Hundreds of items in marketplace
Container Service
The container advantage
Developers love Kubernetes
| Info |
|---|
*According to the new 2020 State of Cloud Native Development Report developed for CNCF by SlashData |
AKS: Simplify the deployment, nanagement, and operations of Kubernetes
| ICON | Description |
|---|---|
| Deploy and manage Kubernetes with ease |
| Accelerate containerized application development |
| Set up CI/CD in a few clicks |
| Secure your Kubernetes environment |
| Scale and run applications with confidence |
| Work how you want with open-source tools & APIs |
Scenarios for AKS
Microservices with AKS
Azure Container Registry
Azure Container Instances (ACI)
Azure App Service
Reference Architecture for Managed Web
| Kind | Architecture | Resources Stack |
|---|---|---|
| Basic Web |
| ✓Service plan ✓Deployment ✓Authentication ✓SQL DB ✓Diagnostics |
| Improving Scalability |
| ✓WebJobs ✓Cache ✓CDN ✓Other storages ✓API App |
| Improving Availability |
| ✓Hosting in paired region ✓Traffic manager ✓Geo-replication |
Serverless stands out as the technology
What is servierless?
| Full abstraction of servers Developers can just focus on their code - there are no distractions around server management, capacity planning, or availability. |
| Instant, event-driven scalability Application components react to events and triggers in near real-time with virtually unlimited scalability; compute resources are used are needed. |
| Pay-per-use Only pay for what you use: billing is typically calculated on the number of function calls, code execution time, and memory used.* *Supporting services, like storage and networking, may be charged separately. |
Azure serverless ecosystem
FaaS is the center of serverless
| ICON | Description |
|---|---|
| Single responsibility Functions are single-purposed, reusable pieces of code that process an input and return a result. |
| Short lived Functions don't stick around when finished executing, freeing up resources for further executions. |
| Stateless Functions don't hold any persistent state and don't rely on the state of any other processes. |
| Event driven & scalable Functions respond to predefined events, and are instantly replicated as many times as needed. |
Azure Functions Programming Model
Scenarios for Serverless
- Anything that needs to respond to events.
Azure Doc: Decision Tree
| Info |
|---|
| Info |
|---|
https://docs.microsoft.com/en-us/azure/architecture/guide/technology-choices/compute-decision-tree |
Bestbuy
| Archetecture | Key Point |
|---|---|
|
|
