Call Us🔝>༒+91-9711147426⇛Call In girls karol bagh (Delhi)
Docker containers
1. Page 1
ERNI – Innovation in Process and Technology
DOCKER CONTAINERS
2. Page 2
ERNI – Innovation in Process and Technology
ABOUT PAU
Almost 15 years in software development
Main technologies:
• Professional .NET developer
• Opensource projects follower
Main interests:
• Domain Driven Design, Distributed systems,
Microservices, Event Sourcing, CQRS, Cloud.
• And now Docker Containers!
3. Page 3
ERNI – Innovation in Process and Technology
ABOUT YOU?
4. Page 4
ERNI – Innovation in Process and Technology
AGENDA
1. ACHITECTURES EVOLUTION
2. KEY TECHNOLOGY : CONTAINERS
3. DISRUPTIVE PRODUCT : DOCKER
4. DEMO TIME!
5. Page 5
ERNI – Innovation in Process and Technology
ARCHITECTURE EVOLUTION – THE
MONOLITH
6. Page 6
ERNI – Innovation in Process and Technology
ARCHITECTURE EVOLUTION – THE
MONOLITH
SHOPPING CART
PRODUCT
CATALOG
SHIPPING MODULE BILLING MODULE
7. Page 7
ERNI – Innovation in Process and Technology
ARCHITECTURE EVOLUTION – THE
MONOLITH
8. Page 8
ERNI – Innovation in Process and Technology
ARCHITECTURE EVOLUTION –
MICROSERVICES
9. Page 9
ERNI – Innovation in Process and Technology
ARCHITECTURE EVOLUTION –
MICROSERVICES
UNIX PHILOSOPHY
•Do one thing and do it well.
•Place well with the others
•Use standard interfaces
10. Page 10
ERNI – Innovation in Process and Technology
ARCHITECTURE EVOLUTION –
MICROSERVICES
11. Page 11
ERNI – Innovation in Process and Technology
ARCHITECTURE EVOLUTION
•1990’s
•Monolith
•Tight Coupling
•2000’s
•Neo Monolith
•SOA
•Looser Coupling
•2010’s
•Microservices
•Decoupled
12. Page 12
ERNI – Innovation in Process and Technology
SCALING LIMITATIONS PROBLEM
13. Page 13
ERNI – Innovation in Process and Technology
DATABASE COUPLING PROBLEM
14. Page 14
ERNI – Innovation in Process and Technology
WHAT‘S WRONG WITH MONOLITHS?
15. Page 15
ERNI – Innovation in Process and Technology
MONOLITH VS MICROSERVICES
•COMPLEXITY
•DEPLOYMENT CYCLE
•TEAMS ORGANIZATION
•SCALABILITY
•TECHNOLOGY STACK
16. Page 16
ERNI – Innovation in Process and Technology
NETFLIX ARCHITECTURE EVOLUTION
•On premises servers
•One big application
•Cloud (AWS)
•100s of microservices
17. Page 17
ERNI – Innovation in Process and Technology
MICROSERVICES VISUALIZATION
EXAMPLES
18. Page 18
ERNI – Innovation in Process and Technology
MICROSERVICES VISUALIZATION
EXAMPLES
19. Page 19
ERNI – Innovation in Process and Technology
NETFLIX FIGURES
20. Page 20
ERNI – Innovation in Process and Technology
NETFLIX FIGURES
21. Page 21
ERNI – Innovation in Process and Technology
GILT FIGURES
22. Page 22
ERNI – Innovation in Process and Technology
ENTERPRISE CLOUD ADOPTION
23. Page 23
ERNI – Innovation in Process and Technology
ABOUT YOU?
STILL AWAKE???
JUST SOME SLIDES TO GO!
24. Page 24
ERNI – Innovation in Process and Technology
AGENDA
1. ACHITECTURES EVOLUTION
2. KEY TECHNOLOGY : CONTAINERS
3. DISRUPTIVE TECHNOLOGY : DOCKER
4. DEMO TIME!
25. Page 25
ERNI – Innovation in Process and Technology
ENABLING MICROSERVICES
ARCHITECTURES
26. Page 26
ERNI – Innovation in Process and Technology
•Key technology: CONTAINERS
•Google has been using container technology for
over 10 years, starting over 2 billion containers
per week
ENABLING MICROSERVICES
ARCHITECTURES
27. Page 27
ERNI – Innovation in Process and Technology
VIRTUALIZATION TECHNOLOGIES
28. Page 28
ERNI – Innovation in Process and Technology
CONTAINERS PROMISES
Faster Uptime
Minutes to Seconds
Smaller Footprint
Gigabytes to Megabytes
More Reliable Deployment
Works everywhere.
Better Scalability
Vertical to Horizontal
29. Page 29
ERNI – Innovation in Process and Technology
AGENDA
1. ACHITECTURES EVOLUTION
2. KEY TECHNOLOGY : CONTAINERS
3. DISRUPTIVE TECHNOLOGY : DOCKER
4. DEMO TIME!
30. Page 30
ERNI – Innovation in Process and Technology
DOCKER SOLUTION
31. Page 31
ERNI – Innovation in Process and Technology
DOCKER ECOSYSTEM
32. Page 32
ERNI – Innovation in Process and Technology
WINDOWS CONTAINERS COMING SOON…
33. Page 33
ERNI – Innovation in Process and Technology
CONTAINERS PROMISES
34. Page 34
ERNI – Innovation in Process and Technology
CONTAINERS PROMISES
35. Page 35
ERNI – Innovation in Process and Technology
QUESTIONS
36. Page 36
ERNI – Innovation in Process and Technology
AGENDA
1. ACHITECTURES EVOLUTION : NETFLIX
EXAMPLE
2. KEY TECHNOLOGY : CONTAINERS
3. DISRUPTIVE TECHNOLOGY : DOCKER
4. DEMO TIME!
37. Page 37
ERNI – Innovation in Process and Technology
DEMO – DOCKER BASICS
Build images, Run containers, DockerHub.
•Installing Docker
•Image vs Container.
•DockerFile
•Basic commands: ps, images, run, commit, build, version,
info
•Build a basic image: nodejs, aspnet
•Windows containers (optional)
38. Page 38
ERNI – Innovation in Process and Technology
DEMO – DOCKER BASICS
39. Page 39
ERNI – Innovation in Process and Technology
DEMO – DOCKER BASICS
40. Page 40
ERNI – Innovation in Process and Technology
DEMO – IMAGE VS CONTAINER
41. Page 41
ERNI – Innovation in Process and Technology
DEMO – DOCKER TOOLS
DOCKER-MACHINE
•Docker toolbox for Windows and MacOSX (optional)
•Provisioning on local VM with Windows client.
•Provisioning on Azure.
•Provisioning on AWS.
DOCKER-COMPOSE
•Startup template download.
•Docker-compose.yml
42. Page 42
ERNI – Innovation in Process and Technology
DEMO – DOCKER TOOLS
43. Page 43
ERNI – Innovation in Process and Technology
DEMO – CONTINUOS DELIVERY
BASIC CONTINUOS DELIVERY PIPELINE: NODE AND
MONGO
•Enable DockerHub for automated Builds.
•Configure CircleCI for automated testing.
•Configure Tutum for containers as a service.
44. Page 44
ERNI – Innovation in Process and Technology
DEMO – CONTINUOS DELIVERY PIPELINE
PUSH
HTTP POST
HTTP POST
HTTP POST
45. Page 45
ERNI – Innovation in Process and Technology
DEMO REFERENCES
DOCKER BASICS: Build images, Run containers, DockerHub.
• https://docs.docker.com/installation/ubuntulinux/
• http://blog.codefresh.io/docker-machine-basics/
• http://www.fireplacecoders.com/?p=15
• http://blogs.msdn.com/b/webdev/archive/2015/01/14/running-asp-net-5-applications-in-linux-containers-
with-docker.aspx
• https://docs.docker.com/introduction/understanding-docker/
DOCKER-MACHINE: Local and Cloud providers
• https://docs.docker.com/installation/azure/
• https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-docker-machine/
• https://docs.docker.com/installation/google/
• http://docs.aws.amazon.com/AmazonECS/latest/developerguide/docker-basics.html#install_docker
• http://networkstatic.net/docker-machine-provisioning-on-aws/
• https://alexanderzeitler.com/articles/a-lap-around-aws-and-docker-machine/
46. Page 46
ERNI – Innovation in Process and Technology
DEMO REFERENCES
CONTINUOS INTEGRATION, CONTINUOS DELIVERY PIPELINE
• http://blog.bananacoding.com/blog/development-workflow-using-docker-and-docker-compose
• http://blog.tutum.co/2015/06/10/node-js-and-continuous-deployment-with-circleci-docker-hub-and-tutum/
WINDOWS CONTAINERS ON LOCALMACHINE AND AZURE
• https://visualstudiogallery.msdn.microsoft.com/0f5b2caa-ea00-41c8-b8a2-058c7da0b3e4
• https://channel9.msdn.com/Blogs/containers/Quick-Start-Provisioning-Containers-using-Visual-
Studio?ocid=player
• https://msdn.microsoft.com/virtualization/windowscontainers/quick_start/manage_powershell
Explain the goal of the talk through the AGENDA
Docker Containers are important for the present and the future.
Monolith advantatges:
Use to them
Tools Refactoring
Easy to get into.
Monolith Problems
Frequent Deploys
Scaling
Developer intimidation
Long commitmentTechnology stack
Monolith Problems:
Frequent Deploys
Scaling
Developer intimidation
Long commitmentTechnology stack
Monolith Problems:
Frequent Deploys
Scaling
Developer intimidation
Long commitmentTechnology stack
Don‘t add more developers, even worse don‘t add more testers… move ON
Don‘a add more definition of done entries
Monolith Problems:
Frequent Deploys
Scaling
Developer intimidation
Long commitmentTechnology stack
Monolith Problems:
Frequent Deploys
Scaling
Developer intimidation
Long commitmentTechnology stack
Monolith Problems:
Frequent Deploys
Scaling
Developer intimidation
Long commitmentTechnology stack
PROBLEMS:
Frequent Deploys
Scaling
Split up teams
Developer intimidation
Long commitmentTechnology stack
Coupling
Relational Database –> eventually consistent
Relational Database –> eventually consistent
Coupling
Availability vs Consistency
CAP Theorem : Resitance to failure.
Internet is microservices architecture: failing all the time.
1M users
Conways law: your architecture looks like your team organizations.
Netflix story
Why do you need a microservice architecture?
Why do you need a microservice architecture?
Cloud Providers are in the epicenter of that revolution.
You haven‘t heard about all this yeet? We‘re almost there.
Tools come from the guys moving to these architectures. 2009
Explain the goal of the talk through the AGENDA
Docker brief history: DotCloud , PAAS
Workflow
Partnership with all the other players enabling microservices.
How an operating system enables microservice?
Creating a really small footprint operating service that can run inside a container.