The Doppler Quarterly Winter 2016 | Page 48

found and containers are rescheduled there . Swarm has container rescheduling planned in the next released .
Scalability and Battle Tested ( Real World Usage )
Mesos is used at a lot of big name companies . Use cases exist at Twitter , eBay , Netflix , and the list goes on . That said , these are real-world use cases for Mesos itself which has a wide ecosystem of frameworks beyond containers . Kubernetes and Docker ’ s Swarm are being used by the development community and have already seen production deployment at a variety of organizations . I expect to see more public references as we go forward .
It ’ s also worth noting that Kubernetes is backed by Google . Google has been running its entire business on containers for a decade and they launch 2 billion containers a week . K8s has made significant strides in the past six months in terms of scalability . With the 1.1 release it now supports clusters with as many as a thousand nodes and one million queries per second .
Swarm has also recently reached “ Production Ready ” status . In testing , it has reached the thousand node mark . It has also seen adoption by some organizations . Most notably is Rackspace which uses Swarm under the hood of their newest container offering . Hortonworks is also using it with their new Cloudbreak project , a provider independent Hadoop as a Service offering .
While Mesos itself has been widely used in the community , Mesosphere and Microsoft are also working together on the new Azure Container Service . This service was announced at MesosCon and should be available in the next few months .
Controllers . That said it ’ s a pretty short learning curve and in return you ’ ll be able to manage at application and service granularity . Mesos , on the other hand , is not for the faint of heart . It can be quite raw and requires a larger skill set for deployment . Mesosphere has made big strides in easing the setup and use of Mesos adoption . The DCOS has just moved to General Availability early this fall . They have built a great management UI and dashboard that integrates with Marathon directly . You can try it out for yourself , for free , on their site .
Cluster Networking
Kubernetes has some of the most straight-forward container networking of the bunch . Network and port management can be a nightmare and is certainly a key area for container management complexity . K8s has some basics tenets in their networking that keep things simple for the developer and reduce the risk in this area considerably . First , they require that all containers communicate with each other without the use of NAT ( Network Address Translation ). They also require the nodes communicate with the containers without NAT . Lastly , K8s requires that a container ’ s internal IP address is the same IP that other containers and nodes use to communicate with it . These tenets eliminate much of the port mapping , address translation , and service discovery issues that arise in large scale operations .
When evaluating solutions for managing Docker containers , nothing is easier than working within the Docker API your team is already used to .
Ease of Adoption ( Skill Set Required )
When evaluating solutions for managing Docker containers , nothing is easier than working within the same Docker API your team is already used to . The Swarm , Compose , Machine trio are built into the core Docker ecosystem so a Docker team should have no trouble picking it up . Kubernetes doesn ’ t require a lot of extra skills to learn and you can even try it out for yourself with this how to ). The biggest difference will be the mental model constructs of Pods , Service , and
Docker has made tremendous strides over the past six months in how it handles networking . The just released 1.9 version has graduated the Docker Networking plugins out of experimental support and into “ Production Ready ” status . The new networking model allows you to create virtual networks independent of the containers . In this way groups of containers can be placed in specific networks as needed . Additionally the networking in Docker allows for the use of plugins if you prefer another model . There are
46 | THE DOPPLER | WINTER 2016