Download to read offline
More Related Content
Similar to How do I run microservices in production using Docker.
![Microcontainers, Microservices, Microservers? Less [Linux] is more!](https://cdn.slidesharecdn.com/ss_thumbnails/belfast-devops-presentation-150916011027-lva1-app6891-thumbnail.jpg?width=640&height=640&fit=bounds)
How do I run microservices in production using Docker.
- 1. Daniël van Gils DeveloperAdvocate @foldingbeauty daniel@cloud66.com www.cloud66.com Running Microservices in Production with Docker
- 2. = public/private/hybrid =yours Services ǽ > 4000 serversEasy Ops tools build for Devs
- 11. • The servicesare easy to replace. • Services are organized around capabilities, e.g., user interface front-end, recommendation, logistics, billing, etc. • Services can be implemented using different programming languages, databases, hardware and software environment, depending on what fits best. microservice architecture ƗƗƗ Ɨ Ɨ ƗƗ Ɨ Ɨ Ɨ Ɨ Ɨ
- 12.
- 14. NOISE $docker run alpineecho 'hello world’ production ? $docker-compose up -d time skills
- 15. Ɨ ǽ #1 the rightcontainer image #2 containers in production ƗƗ microservice example
- 16. service Ɨ containers server cluster(s)Ȑ imageƗǽ ƗƗ =code = docker file = docker engine = platform Ɨ build ship deploy
- 17.
- 18.
- 19. Ɨ ƗƗǽ Ɨǽ I can bake1 donut in x seconds. message queue I want 5 donuts request 5 donuts donuts are baking donuts are ready I know how to receive orders and give orders to baking minions.
- 20.
- 28.
- 38.
- 39.
- 40.
- 43.
- 46. Ɨǽ ƗƗ integration test +development Ɨǽ ƗƗ Ɨǽ ƗƗ Ɨǽ ƗƗ
- 48.
- 49. you can’t polisha turd Ɨ containerization Ǹ Dž ƗƗƗ =
- 50. Ɨǽ “The right imageshould be the same in all your environments.”
- 51. Ɨǽ “The right testsshould be the same in all your environments.”
- 52. Ɨǽ “I didn't havetime to create a slim image, so I created a fat one instead.”
- 53. Ɨǽ “The right imageneeds at least 5 kisses” kiss = keep an image s…, smart ass slim secure speedy stable set
- 54. SLIM Start with thesmallest minimal image you can find and trust. Remove compile time dependencies. Remove packages you don’t need. Squash layers to reduce size. Run stats for the image. habitus.io blog.cloud66.com Ɨǽ
- 57.
- 58. SECURE Remove all thesecrets. Patch to the latest security updates. Run the image with the right UID. Test the image. https://github.com/docker/ docker-bench-security Ɨǽ
- 59.
- 60. SPEEDY Optimize code. Memory andcpu usage. One process. Load testing. Ɨǽ
- 61.
- 62. STABLE Lock the imageversion. Lock the runtime version(s). Tag your image. Proper logging. Ɨǽ
- 63.
- 64. SET Use volumes wisely,use external services for persistency, don’t abuse host system. Loosely coupled. Remove things which are hard to maintain in production. Ɨǽ
- 66.
- 67. Ɨǽ Ɨ monolith containerization± 70 % (multi tenant) monolith 1x monolith image FAT
- 68. Ɨǽ Ɨ API first containerization± 20% Ɨǽ Ɨ api 1x frontend 1x image frontend FAT image api FAT
- 69. Ɨǽ Ɨ splitting monolith containerization± 6% Ɨǽ api 6x frontend 1x Ɨǽ Ɨ workers 10x ƗƗƗ ƗƗƗƗ ƗƗ image frontend FAT image api THIN image workers THIN ƗƗƗ ƗƗ Ɨ
- 70. Ɨǽ Ɨǽ A 6x B 12x Ɨǽ Ɨ C10x ƗƗƗ ƗƗƗƗ ƗƗ image B THIN image A THIN image C THIN ƗƗƗ ƗƗ Ɨ microservice architecture ± 4% ƗƗƗ ƗƗ ƗƗ ƗƗ ƗƗ Ɨ message queue
- 71.
- 72.
- 74. Choose your platformwisely.
- 75.
- 76.
- 77. LIFECYCLE Have an imageguideline. Create a workflow using the same image in all the software cycle stages. From design to production mimic the environment. Test heavily. Ǻ
- 78.
- 79. ORCHESTRATION Provisioning nodes. Networking. Isolation ofservices. Self healing. iOi = Infrastructure on Infrastructure. Ǻ
- 80.
- 81. DISCOVERY Find your servicesand datasources with minimal code change. Versioning of running services. Automagically update discovery when services come and go. Ǻ
- 82.
- 83. SCALING/SCHEDULING Scale your service(= more running containers). Scale your nodes. Scale your on/off jobs. Failover groups. Hybrid infrastructure. Load balancing. Ǻ
- 84.
- 85. DATA MANAGEMENT Backup andrestores. Clustering. Verify your backups. Ǻ
- 86.
- 87. MONITORING Get all thestatistics of resources (mem/load/net/res) used. Aggregating of logs. Key debugging ingredient. Ǻ ǟ
- 88.
- 89. SECURITY Node and Enginelevel. Intrusion detection and prevention systems. DoS protection. Firewall. Segregate container groups Verification of images. Ǻ Ǻ
- 90. Choose your platformwisely.
- 91. When you getDevOps, Testing, Microservices architecture right and creating the right minimal lovable Image and having the right platform to run containers. Happy Camper. ǽ
- 92. THANK YOU www.cloud66.com (freedocker in production platform trial) www.codefresh.com www.habitus.io (open source docker build flow tool) startwithdocker.com (easy starter for docker) https://github.com/cloud66-samples/webinar_codefresh ``` Ɨǽ Daniël van Gils Developer Advocate @foldingbeauty daniel@cloud66.com www.cloud66.com