Chapter 7. Implications of Using DC/OS
Moving to Mesos was a huge operational win. We codified our configurations and can deploy slowly to preserve hit-rate and avoid causing pain for persistent stores as well as grow and scale this tier with higher confidence.1
In this report, I have explained how DC/OS works and how you can use it to run software applications and services. In this chapter, I take a step back and explain at a high level what DC/OS does, which I think is most exciting. I will then get back into the detail and explore the specific benefits of using DC/OS from different perspectives and show that it meets the requirements set out in the first chapter.
Successful cloud platforms such as Amazon Web Services (AWS), Microsoft Azure, and a Google Cloud Platform enabled companies like Netflix and Snapchat to build scalable businesses. Each individual platform provides a range of high-level services that can be configured and managed with a single set of tools. Major tech companies such as Facebook and Google have built similar platforms internally. DC/OS is exciting to me because it can provide a comparable platform and suite of high-level services to any company, whether they want to run in the cloud or in private datacenters.
By building on top of Mesos and Docker, DC/OS abstracts away concerns about hardware, operating systems, and the locations of running services. What this provides is an abstraction for applications that is analogous to the abstraction for machines ...
Get Application Delivery with DC/OS now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
