1. Modern Application Platform Windows Server 2016
5/27/2018
Modern Application Platform Windows Server 2016
Speaker, date
Slide 1: Slide title here
Speaker notes
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

2. Agenda Application Evolution Windows Server 2016: Modern App Platform
Recap and Next Steps

3. Agenda Application Evolution Windows Server 2016: Modern App Platform
Recap and Next Steps
Recap and Next Steps

4. Cloud service delivery
Tension drives change
Business Turbulence and innovation
Cloud service delivery
There is a fundamental tension between the needs of the business and how Central IT enables those needs
Business is moving faster today than ever before and people are needing to react more quickly to changing market dynamics
But this is exciting because in this chaos is opportunity and there is a lot of value being created through these ups and downs
This is create for the business, but challenging for Central IT
Traditionally the needs of the business have resulted in a direct correlation to the demands placed on Central IT (e.g. new application features, new marketing campaign, etc.)
The problem is that while the business finds opportunity in chaos and uncertainty, Central IT is exactly the opposite and strives for stability, control and predictability
Therefore the faster business cadence is putting increased pressure on Central IT and the model is not sustainable
<click>
The solution is to provide a layer of abstraction between the two and this is at the heart of what cloud computing is all about. Provide the business all the tools they need to take advantage of opportunities while allowing Central IT to retain the control and stability required to run an enterprise-class datacenter.
So let’s talk a bit more about the “Transition to the Cloud”
<click to next slide>
IT Stability and predictability

5. Application evolution
Traditional, legacy applications
Monolithic apps that take advantage of Scale-Up
Cloud-native apps and micro-services
Containerized apps, spanning IaaS and PaaS that take advantage of Scale-Out
Deployment Choices
Single Machine
Multi Tiered
Cloud Native

6. Application evolution
Traditional, legacy applications
Monolithic apps that take advantage of Scale-Up
Cloud-native apps and micro-services
Containerized apps, spanning IaaS and PaaS that take advantage of Scale-Out
Deployment Choices
IT Investments
Focus on the infrastructure to avoid application problems
Focus on the application to avoid infrastructure problems
Single Machine
Multi Tiered
Cloud Native

7. “Born-in-the-cloud” applications
Designed for cloud agility, elasticity, and scalability
Constant innovation and upgraded features
Shared services allow for increased speed
Options to leverage dynamic data sources

8. Write once, deploy anywhere
Server & Tools Business
5/27/2018
Write once, deploy anywhere
Virtual machines
Containers
Azure Service Fabric
Azure Resource Manager
Microsoft Azure Stack
Microsoft Azure
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

9. Agenda Application Evolution Application Evolution
Windows Server 2016: Modern App Platform
Recap and Next Steps
Recap and Next Steps

10. What is a container?
Traditional virtual machines = hardware virtualization
Application VM VM VM VM VM … OS
Hardware
Hardware
Containers = Operating system virtualization
CONTAINER
CONTAINER
CONTAINER
CONTAINER
CONTAINER OS …
Processes
Kernel
Kernel

11. Windows Server Containers Anatomy and key capabilities
5/27/2018 4:38 PM
Windows Server Containers Anatomy and key capabilities
Container A
Container B
Container C
Spotlight capabilities
Web tier
App tier
DB tier
Build: write, run, and scale within containers
Run: container capabilities built into Windows Server
Manage: deploy and manage using PowerShell
Resources: define resources per container
Network: IP options for connectivity
LOB app (+Binaries)
LOB app (+Binaries)
LOB app (+Binaries)
Libraries (Shared across containers)
Libraries
Build: Developers will use familiar development tools, such as Visual Studio, to write apps to run within containers.
By building modular apps leveraging containers, modules can scale independently, and be updated on independent cadences.
Run: Container capabilities built into Windows Server
Manage: Deploy and manage containers using PowerShell, or using Docker.
Resources: Define CPU and memory resources per container along with storage and network throughput.
Network: Provide NAT or DHCP/static IP for network connectivity.
So what are some of the core Windows Server container capabilities.
The first key takeaway, is that there is core functionality for containers, supported natively within the kernel, and they will be available in the next release of Windows Server.
Developers will use familiar development tools, such as Visual Studio, to write apps to run within containers. Instead of trying to backport existing applications, by building modular apps leveraging containers, modules can scale independently, and be updated on independent cadences, providing the developer with much greater flexibility and speed.
Applications can rely on other packages to provide core functionality. As you can see from the graphic, there are 2 containers that are sharing a number of libraries. In addition, when packaging, the packages also depend on a base package which describes the underlying operating system, such as Server Core, which has a large number of APIs that Windows supports, such as .NET, IIS etc. Nano Server is another, however this has a much smaller surface, that will target apps that have been written from the ground up, with the cloud in mind.
Containers are isolated behind their own network compartment. This can be provided a NAT DHCP or Static IP. Each container has an independent session namespace, which helps to provide isolation and additional security. The kernel object namespace is isolated per container.
Each container also has access to certain CPU and memory resources, along with storage and network capacity – these are controlled by the administrator, and ensures predictable and guaranteed control of processes.
These containers can be managed using tools such as PowerShell, or using the Docker management tools.
Host OS w/Container Support
Server (Physical or Virtual)
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

12. Hyper-V Containers Anatomy and key capabilities
5/27/2018 4:38 PM
Hyper-V Containers Anatomy and key capabilities
Hyper-V Container
Hyper-V Container
Spotlight capabilities
Consistency: consistent container APIs
Compatibility: identical container images
Strong isolation: dedicated kernel copy
Highly trusted: proven Hyper-V technology
Optimized: virtualization layer and OS optimized
App A
Bins/Libraries
App A
Bins/Libraries
Windows Guest OS Optimized for Hyper-V Container
Windows Guest OS Optimized for Hyper-V Container
Consistency: Hyper-V Containers use the same APIs Windows Server Containers ensuring consistency across management and deployment toolsets.
Compatibility: Hyper-V Containers use the exact same images as Windows Server Containers.
Strong Isolation: Each Hyper-V container has it’s own dedicated copy of the kernel
Highly Trusted: Built with proven Hyper-V virtualization technology.
Optimized: The virtualization layer and the operating system have been specifically optimized for containers
Hyper-V Containers take a slightly different approach to containerization. To create more isolation, Hyper-V Containers each have their own copy of the Windows kernel and have memory assigned directly to them, a key requirement of strong isolation. We use Hyper-V for CPU, memory and IO isolation (like network and storage), delivering the same level of isolation found in VMs. Like for VMs, the host only exposes a small, constrained interface to the container for communication and sharing of host resources. This very limited sharing means Hyper-V Containers have a bit less efficiency in startup times and density than Windows Server Containers, but the isolation required to allow untrusted and “hostile multi-tenant” applications to run on the same host.
So aren’t Hyper-V Containers the same as VMs? Besides the optimizations to the OS that result from it being fully aware that it’s in a container and not a physical machine, Hyper-V Containers will be deployed using the magic of Docker and can use the exact same packages that run in Windows Server Containers. Thus, the tradeoff of level of isolation versus efficiency/agility is a deploy-time decision, not a development-time decision – one made by the owner of the host.
Hypervisor
Server
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

13. Demo
Windows Server Containers

14. New deployment option: Nano Server
5/27/2018
New deployment option: Nano Server
Just enough OS
Optimized for modern applications
Higher density and performance
Reduced attack surface and servicing requirements
Next-gen distributed app frameworks
Interoperate with existing server applications
Third-party applications
RDS experience
Traditional VM workloads
Just enough OS: Simplified deployment Improved resource utilization Reduced servicing requirements
Containers and modern applications
Full GUI
Specialized workloads
Server Core
Lower maintenance server environment
Nano Server
Just enough OS
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

15. Microsoft Ignite 2015
5/27/2018 4:38 PM
Nano Server goals
DevOps mindset: "Treat servers like cattle, not pets"
Goal: Eliminate the need to ever sit in front of a server
Remote graphical and web-based management tools
Remote management and automation via PowerShell & WMI
© 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

16. Nano Server: Developer Experience
Full developer experience, unlike Server Core
Windows SDK & Visual Studio 2015 target Nano Server
Rich design-time experience
Full remote debugging experience

17. Demo
Nano Server

18. Optimized for containers
Nano Server
Server Core
Highly optimized
Born-in-the-cloud applications
Highly compatible

19. Azure Service Fabric Microservice-based applications Service Fabric
Scalability
Availability
Performance
Lifecycle management
Portability
Monitoring
Enterprises and ISVs are looking to new Microservices architectures to support new DevOps agile processes to get new capabilities into production and delivering value faster than ever before. These new applications run as always-on, scalable services and to save developers from building middleware, we built Azure Service Fabric <CLICK>
Azure Service Fabric is a distributed application platform that hides the underlying infrastructure while enhancing <CLICK> scalability, availability, performance, application lifecycle management, cloud portability and monitoring of the application.
Our vision for Service Fabric is that it will provide the same platform benefits <CLICK> which ever cloud the application is deployed to, whether Azure, Private Cloud in customers’ own datacenter or other public and hosted clouds.
We started building Service Fabric over 10 years ago and today run many core Azure services on it including InTune and over 1.4 million SQL databases.
Building on Azure Service Fabric means:
Developers focus on writing code to deliver business value, not middleware features
Operating services reliably, at scale and with low latency becomes much easier with less operating cost due to the level of automation built into Service Fabric
Moving workloads between clouds and preventing lock-in is simple as Service Fabric enjoys support in multiple clouds and on-premises
For ISVs this means you can convert your on-premises software into always-on, reliable, scalable SaaS offerings without the time or expense of writing complex code to deal with failures in the infrastructure and the headache of managing frequent updates to a live service.
For System Integrators, Service Fabric enables you to rapidly create low-latency back-end services for your clients that run on-premises or in the cloud, without the expense and time often required to build unique software frameworks for availability, scalability and application lifecycle management.
Azure
Developers focus on features not infrastructure
On-premises
Automation ensures service scalability and reliability
Multi-cloud support for maximum portability
Other clouds

20. Agenda Application Evolution Application Evolution
Windows Server 2016: Modern App Platform
Windows Server 2016: Modern App Platform
Recap and Next Steps

21. Modern application platform recap
Server & Tools Business
5/27/2018
Modern application platform recap
Virtual machines
Containers
Azure Service Fabric
Azure Resource Manager
Microsoft Azure Stack
Microsoft Azure
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

22. Next steps
Download the latest Technical Preview for Windows Server: us/evalcenter/evaluate-windows-server-technical- preview
Check out the documentation for Windows Server Containers:
Check out the documentation for Nano Server:
Check out the Containers Channel:

23. © 2015 Microsoft Corporation. All rights reserved
© 2015 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.