Microsoft deck from Cloud-Native Workshop

3. Dev
Ops
IT Decision Maker
Runtime App Monitoring
App Lifecycle
Management
Manage Services Not
Servers
Auto OS UpdateAuto Scale
No vendor
Lock-in
High Density
Custom OS
Hybrid Support

4. Azure Compute Platform Overview
Azure
Virtual Machines
VM Scale Sets
Service
Fabric Apps
App Service
Media
Services
Power
Apps
Azure
Functions
Stream
Analytics
Rapid
Development
High Control
Web/
Mobile
PaaS
IaaS

6. Build on Dev frameworksBuild on Infrastructure
Cloud Foundry In the Azure Ecosystem
“App Creators”
Developers Analysts
Microsoft Azure
LOBSaaSLift & Shift Docker
Virtual
Machines
Stateful and
stateless one-
off solutions
VM Scale
Sets
Scalable
solutions
Container
Service
Scalable,
orchestrated
Docker images
deployed into
containers
Differentiation Time to valueExisting App Investments
Batch
Custom High
Performance
Computing
solutions
Open
Source
PaaS
Cloud
Foundry
Service
Fabric
Custom
Microservice-
based
stateless and
stateful
solutions
Power
Apps
Graphical
design
mobile
solutions
App Service
Template based
rapid
development
web, mobile and
API solutions
Orchestrated
workflow
based
integration
solutions
LogicWeb/Mob/
API
All the
goodness of
App Service
in a
dedicated
environment
Environments

7. Asked frequently by our customers
‘Open Source’ is the key
Great option for Java
Give the customer the choice
Growing CF communities among enterprises
CF on Azure : Why should we care about?

9. Public, Global, Shared Datacenters
Applications
Azure Interfacehttp://
Push App
> cf

10. Fully Open Sourced
Dedicated Engineering Team
Aligned with Community’s
engineering practices
Committed Engineering Roadmap
Designed for Azure and Azure
Stack
More about Azure Bosh CPI

11. Network Services
Application Services
Azure Virtual Machines
Microsoft Azure
Storage
SQL Database
Service Bus
DocumentDB
Virtual Network VPN Gateway
Enterprise HQ
PCF + Azure Logical Architecture

12. Marketplace Services

13. Azure Logical Architecture

14. Azure Availability Sets and Fault Domains
Standard Deployment using Availability Zones Azure Deployment using Availability Sets and Fault
Domains

15. Azure Network Topology

17. Visual Studio Team Services IntegrationVisual Studio Team Services CF Integration

18. Microsoft OMS Integration for PCFMicrosoft OMS Integration with PCF

20. Direct deployment from a single click -

21. Kevin Hoffman :
Beyond the Twelve-
Factor App
https://content.pivotal.io/ebooks/beyond-the-12-factor-app

22. Twelve Factor Application -
I. Codebase
One codebase tracked in revision control, many deploys
II. Dependencies
Explicitly declare and isolate dependencies
III. Config
Store config in the environment
IV. Backing services
Treat backing services as attached resources
V. Build, release, run
Strictly separate build and run stages
VI. Processes
Execute the app as one or more stateless processes
VII. Port binding
Export services via port binding
VIII. Concurrency
Scale out via the process model
IX. Disposability
Maximize robustness with fast startup and graceful shutdown
X. Dev/prod parity
Keep development, staging, and production as similar as possible
XI. Logs
Treat logs as event streams
XII. Admin processes
Run admin/management tasks as one-off processes

23. The Next Three Factors -
XIII. API First
Create experiences and products which work across may devices.
API First frees organizations from the waterfall,
deliberately engineered systems that follows a
preplanned orchestration pattern, and allows
products to evolve into organic, self-organizing
ecosystems that can grow to handle new and
unforeseen demands
- Kevin Hoffman

24. The Next Three Factors -
XIV. Telemetry
Gather data not only about the application, but also from the domain. Correlate specific health metrics
including system logs to the full data spectrum. It becomes exponentially more difficult to identify issues and resolve
root cause problems as we scale horizontally.
With over 65 million units sold, Halo is one of the most
popular game franchises of all time. Microsoft need to
keep sophisticated telemetry to be successful not only for
the game but also for the hardware it used in the Azure
cloud environment. In addition domain information and
operational intelligence to make quality match making for
multiplayer mode.
Fun Fact – Halo ingests hundreds of billions of events on a
given day with sustained peaks above the one million
requests a second

25. The Next Three Factors -
XV. Authentication and Authorization
Security should never be an afterthought.
A cloud-native application by default is a secure
application. Code that is complied or raw living In a public
data center, cloud, or even on-premise location
should be safe guarded by role-based access control (RBAC)
RBAC is a approach to restricting system access to authorized
users.