When to consider
Benefits
Core technologies
|
When to consider
Benefits
Core technologies
|
When to consider
Benefits
Core technologies
|
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 |
| 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 |
Modernize business critical applications | SaaS delivery | Real-time telemetry | Geo-distributed applications |
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. |
*According to the new 2020 State of Cloud Native Development Report developed for CNCF by SlashData |
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 |
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 |
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. |
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. |
https://docs.microsoft.com/en-us/azure/architecture/guide/technology-choices/compute-decision-tree |
Archetecture | Key Point |
---|---|
|