sharepoint saturday cambridge 2016 session
TRANSCRIPT
Extending Office Add-ins with the Azure Container Service
Rick Van RousseltSharePoint Saturday Cambridge
Rick Van RousseltRivaro Consultancy
Office 365 / SharePoint consultant
Working with SharePoint since 2010
Currently focussed on Office 365 and Azure
Email : [email protected]
rickvanrousselt
Agenda
• Docker and containers quick intro
• Why use Docker• Azure Container Service• Using containers with
Office Add-ins
docker and containers- Ligthweight, open secure platform
- Simplify building, shipping, running apps
- Shipping container system for code
Virtual Machines
Each Guest OS needs:• CPU• RAM• Licensing• Maintenance
Containers
• More room for apps• Lesser maintenance• Licensing
Docker major components
• Engine (a.k.a. deamon, runtime)
• Images
• Containers
Docker Engine
Docker engine Docker engine
• Blueprint or definition of a container (readonly)• Needed by docker engine to create a running
instance of a container• Can consist out of multiple layers
Code Node.js UbuntuImage
Images
Containers
• Running instance of an image
• Runs the app
• Isolated and secured
Run everywhereDEMO
V1 V2 V3
Why use containers
Eliminate app conflicts
DEV TEST PROD
Why use containers
Easy app shipping
It’s just easy for us developers
• When joining an ongoing project not need to do a
long setup for a developer environment
• No need for heavy virtual machines
• Development environment is almost the same as
production
Why use containers
The SharePoint
Context
Why use containers
Connecting to Office 365 groups from a container
Demo
Azure Container Service
What is the Azure Container Service- Optimised for
hosting containers- Easy to manage
containers at very large scales
- Docker swarm and DC/OS included
- Open source
DC/OS vs docker Swarm
• Large scale• Proven in production
environments• Complex
• Native from docker
• Standard docker interface
Overview of the Azure Container ServiceDemo
What’s in it for us
Automated buildsDemo
