Book Image

Apache Mesos Cookbook

By : Marco Massenzio, Blomquist, Tomasz Janiszewski
Book Image

Apache Mesos Cookbook

By: Marco Massenzio, Blomquist, Tomasz Janiszewski

Overview of this book

Apache Mesos is open source cluster sharing and management software. Deploying and managing scalable applications in large-scale clustered environments can be difficult, but Apache Mesos makes it easier with efficient resource isolation and sharing across application frameworks. The goal of this book is to guide you through the practical implementation of the Mesos core along with a number of Mesos supported frameworks. You will begin by installing Mesos and then learn how to configure clusters and maintain them. You will also see how to deploy a cluster in a production environment with high availability using Zookeeper. Next, you will get to grips with using Mesos, Marathon, and Docker to build and deploy a PaaS. You will see how to schedule jobs with Chronos. We’ll demonstrate how to integrate Mesos with big data frameworks such as Spark, Hadoop, and Storm. Practical solutions backed with clear examples will also show you how to deploy elastic big data jobs. You will find out how to deploy a scalable continuous integration and delivery system on Mesos with Jenkins. Finally, you will configure and deploy a highly scalable distributed search engine with ElasticSearch. Throughout the course of this book, you will get to know tips and tricks along with best practices to follow when working with Mesos.
Table of Contents (9 chapters)

Introduction


In 2006, engineers from Google started working on enabling the running of applications in separated environments on the Linux kernel. This was not a new approach. Similar techniques were used in BSD Jails and Solaris Zones. In 2013, Docker became publicly available. The container revolution started and Docker became a synonymous with container. For developers, containerization meant that they could pack their application with all dependencies and it would run exactly the same as on their machines as it would on their machines. For admins, containers meant less configuration coupling between the machine and applications because applications contained definitions for all dependencies. In the long run, containers are significantly cheaper than virtual machines.