Ad
More Related Content
Viewers also liked (9)
Similar to How the hell do I run Docker in production, and will it scale? (20)
Ad
Recently uploaded (20)
Ad
How the hell do I run Docker in production, and will it scale?
- 1. Daniël van Gils @foldingbeauty [email protected] www.cloud66.com How the hell do I run Docker in Production?... and will it scale?
- 3. Established in 2012 Build, deploy and maintain any application on any server, on the cloud provider of your choice or bring your own servers. Running Docker in production for almost 1½ years for our customers. We simplify DevOps. Average of 4000+ servers.
- 4. How the hell do I run Docker in Production?... and will it scale? Daniël van Gils @foldingbeauty [email protected] www.cloud66.com
- 7. NOISE $docker run alpine echo 'hello world’ you don’t know what kind of skills you need production you know what kind of skill you need you think you know your gained all the skills but you don’t know time skills
- 9. Ɨ ǽ #1 the right container image #2 containers in production ƗƗ
- 12. Containers need a smooth DevOps team
- 13. service Ɨ containers server cluster(s)Ȑ imageƗǽ ƗƗ = code = docker file = docker engine = platform Ɨ build ship deploy
- 16. you can’t polish a turd Ɨ containerisation Ǹ Dž ƗƗƗ =
- 17. Keep Images Slim Stupid dev » test » stage » production ǽ Minimal Lovable Service Image
- 18. SMALL SECURE SPEEDY / PERFORMANT STABLE SET / IMMUTABLE Ɨǽ Keep Images Small, Secure, Speedy, Stable and Set Stupid
- 19. SMALL Start with the smallest minimal image you can find. Remove compile time dependencies. Remove packages you don’t need. Run stats for the image. Ɨǽ “I didn't have time to create a slim image, so I created a fat one instead.”
- 21. SECURE Remove all the secrets. Patch to the latest security updates. Run the image with the right UID. Test the image. Ɨǽ
- 23. PERFORMANT Optimise code. Memory and cpu usage. One process. Load testing. Ɨǽ
- 25. STABLE Lock the image version. Lock the runtime version(s). Tag your image. Proper logging. Image guideline for your team. Ɨǽ
- 27. IMMUTABLE Use volumes wisely. Loosely coupled. Don’t use databases inside a image. Use external services for persistency. Ɨǽ
- 28. dev » test » stage » production ǽ Minimal Lovable Service Image Keep Images Small, Secure, Speedy, Stable and Set Stupid
- 30. Ɨǽ Ɨ monolith containerisation ± 70 % monolith 1x monolith image FAT
- 31. Ɨǽ Ɨ API first containerisation ± 20% Ɨǽ Ɨ api 1x frontend 1x image frontend FAT image api FAT
- 32. Ɨǽ Ɨ splitting monolith containerisation ± 6% Ɨǽ api 6x frontend 1x Ɨǽ Ɨ workers 10x ƗƗƗ ƗƗƗƗ ƗƗ image frontend FAT image api THIN image workers THIN ƗƗƗ ƗƗ Ɨ
- 33. Ɨǽ Ɨǽ A 6x B 12x Ɨǽ Ɨ C 10x ƗƗƗ ƗƗƗƗ ƗƗ image B THIN image A THIN image C THIN ƗƗƗ ƗƗ Ɨ microservice architecture ± 4% ƗƗƗ ƗƗ ƗƗ ƗƗ ƗƗ Ɨ message queue
- 35. DEV/OPS/DESIGN FLOW Have an image guideline. Create a workflow using the same image in all the software cycle stages. From design to production mimic the environment. Test heavily. Ǻ
- 37. ORCHESTRATION Isolation of services. Make use of the resource available. Self healing. Load distribution. Adding nodes to your cluster. Ǻ
- 39. DISCOVERY Find your services and datasources with minimal code change. Versioning of running services. Automagically update discovery when new services are online or scaled up/down. Ǻ
- 40. DEV/OPS/DESIGN FLOW ORCHESTRATION DISCOVERY SCALING/SCHEDULING DATA MANAGMENT MONITORING SECURITY
- 41. SCALING/SCHEDULING Scale your containers. Scale your docker cluster. Scale your on/off jobs. Failover groups. Cross cloud clusters. Load balancing. Ǻ
- 43. DATA MANAGEMENT Backup and restores. Clustering. Verify your backups. Run natively not in a container for non cloud native DBs. Ǻ
- 45. MONITORING Get all the statistics of resources (mem/load/net/res) used. Aggregating of logs. Debugging your containers. Ǻ ǟ
- 47. SECURITY Intrusion detection and prevention systems. Denial of service protection. Firewalling. Failover groups. Segregate container groups VPC / bastion servers. Verification of images. Ǻ Ǻ
- 49. When you get DevOps right, Microservices architecture right and creating the right minimal lovable Image and having the right platform to run containers. Ohh man, the future is bright and you don’t go to hell! ǽ
- 50. www.cloud66.com blog.cloud66.com habitus.io startwithdocker.com ready for your quest? thank you Daniël van Gils @foldingbeauty [email protected] www.cloud66.com