Why re-purposing VM based app delivery tooling for container delivery at scale is ineffective.

1. Containers
as a unit of packaging and
deploying apps has
become dominant.
Copyright 2018-19, WaveMaker Inc., All rights reserved
Portable | Fast | Economical
200%
Increase in enterprises
deploying more than
250 containers
80%
Expected increase in
containerized apps
over the next 2 years

2. With VM’s
DevOps teams
Setup VMs with O.S and app stack
Build, deploy, configure app artifacts on a
running VM
Copyright 2018-19, WaveMaker Inc., All rights reserved
With containers
App updates
Running VM is updated, reconfigured
using scripts
DevOps teams
Create a single container image
pre-built with config and app artifacts
App updates
Container Images are rebuilt
and redeployed
Fixing issues
Fixed by logging into the VM and
modifying it
Fixing issues
Containers are not modified, gets replaced
from a new image that contains the fix

3. Copyright 2018-19, WaveMaker Inc., All rights reserved
Created more often
Every microservice needs a dedicated container
Replaced frequently
95% of containers live less than a week
Unlike VMs
Containers are ...

4. revolution,
not
evolution.
Delivery workflow for
containers needs a
Copyright 2018-19, WaveMaker Inc., All rights reserved
Repurposing VM tools is ineffective
Microservices are generated in 1000’s
Scripts and manual steps cause bottlenecks
Ops and Dev can’t act in silos
Visually manage dependencies and configurations
Container images are immutable
Extensive standardization is needed for voluminous builds

5. For continuous
delivery of apps
as containers
Copyright 2018-19, WaveMaker Inc., All rights reserved
build time is as
important as
runtime*.
. . . .
*

6. Apps as
containers
built and delivered at scale.
Copyright 2018-19, WaveMaker Inc., All rights reserved
HyScale