Microservice architecture is becoming a very popular way to design your application. Generally, these systems will run many containers across many physical machines. To manage this complexity, the term "orchestration" has been applied to the system that schedules containers onto machines. Tools like Kubernetes, Mesosphere and Docker Swarm are 3 of the orchestration platforms that modern, Docker based stacks can use to do this. These tools will constantly make scheduling decisions that may result in moving a container from one machine to another. There is a bit of the picture missing - what happens when a container writes some state to disk? Now the orchestration platform cannot move that container from one host to another because the data will be left behind. This is the problem that Flocker aims to solve and in this talk I will discuss how Flocker does this and what it means for being able to deploy stateful containers using orchestration frameworks.

YOU MAY ALSO LIKE:

• Keynote: Running database containers using Marathon and Flocker (SkillsCast recorded in November 2015)
• Fast Track to Chaos Engineering with Russ Miles (in London on 6th - 8th November 2019)
• Fast Track to RESTful Microservices (in London on 11th - 13th November 2019)
• Scala eXchange London 2019 (in London on 12th - 13th December 2019)
• µCon London 2020 - The Conference on Microservices, DDD & Software Architecture (in London on 27th - 29th May 2020)
• Keynote by Brian Ketelsen on Going Multicloud with Serverless (in London on 17th October 2019)
• 2 Presentations: Kubernetes Ingress & DevOps and Microservices Better Together (in London on 17th October 2019)
• Turbocharging Azure DevOps with Octopus Deploy (SkillsCast recorded in October 2019)
• Building an open source Cloud-native Edge Computing infrastructure with the OpenNESS Toolkit for 5G and Industry 4.0. (SkillsCast recorded in October 2019)