To watch the recording of this webinar please use the below URL: http://wso2.com/library/webinars/2016/07/achieving-economies-of-web-scale-in-your-enterprise-with-containerization/ Containers are the next big step in cloud architectures. Unlike virtual machines, containers share the same underlying operating systems. This leads to significantly smaller overhead and higher efficiency. Orchestration technologies such as Kubernetes allow to achieve scale by managing multi-container deployments. Containers enable microservice architectures, near-instant scaling, application portability and cross-datacenter solutions. In this webinar, Dmitry will explore how these technologies can bring the cloud economies of scale to your data center.

1. Achieving Economies of
Web Scale
in Your Enterprise
with Containerization
Dmitry Sotnikov
VP, Cloud

2. Containers are Taking over the World

6. What are containers?
Why the fuzz?
Are containers = microservices?
How to realize the benefits?

7. Image credit: Docker Inc.

8. 1979 chroot
2000 FreeBSD Jails
2001 Linux VServer
2004 Solaris Containers
2005 OpenVZ
2006 Process Containers
2007 Control Groups
2008 LXC
2011 Warden
2013 Docker

9. Docker is Different
o Efficient layered container image model
o Global and local container repositories
o Clean management interfaces:
o CLI,
o REST API

10. Container Benefits: Portability
o Docker image includes all dependencies
o Works the same on developer machine,
QA environment, and production
o No “works on my machine” issues
o No environment troubleshooting
o Enables devops approach

11. Container Benefits: Lightweight
o No OS overhead
o Higher density
o Enable microservices architecture

12. Monolithic Architecture

13. Microservices Architecture

14. Inventory
Accounting
Shipping
Store
Monolithic Architecture

15. Microservices Architecture
Inventory
Accounting
Shipping
Store

16. Microservices Architecture
Inventory
Accounting
Shipping
Store
Inventory
Accounting
Shipping
StoreStoreStore

17. Container-Native Architecture
o Rapid boot and start
o Low memory footprint
o Single function
o Immutable – no deployment
o Disposable
o No request dispatching
o Sustains failures
o Rapid independent scaling

18. Getting There
o Experiment with new projects
o Evaluate container
orchestration technologies
o Pay attention to interfaces,
integration, common identity
model, analytics
o Gradually rebuild existing
systems

19. Contact us !