Apache Mesos: Difference between revisions
No edit summary |
Fixed link Tags: Mobile edit Mobile web edit Advanced mobile edit |
||
(63 intermediate revisions by 45 users not shown) | |||
Line 1: | Line 1: | ||
{{Short description|Software to manage computer clusters}} |
|||
{{Infobox software |
{{Infobox software |
||
| name |
| name = Apache Mesos |
||
| logo |
| logo = [[File:Apache_Mesos_Logo.svg|250px|Apache Mesos Logo]] |
||
| screenshot |
| screenshot = |
||
| caption |
| caption = |
||
| developer |
| developer = [[Apache Software Foundation]] |
||
| latest release version = 1. |
| latest release version = 1.11.0 |
||
| latest release date = {{Start date and age|2020|11|24}}<ref>{{cite web|url=https://gitbox.apache.org/repos/asf?p=mesos.git;a=tag;h=c21c1c905d729e9fe93d328677d1a4e3a65d7e20|title=ASF Git Repos - mesos.git/tag|access-date=27 September 2022}}</ref> |
|||
| latest release date = {{release date|2017|11|16}} |
|||
| repo = {{URL|https://gitbox.apache.org/repos/asf/mesos.git|Mesos Repository}} |
|||
| programming language |
| programming language = [[C++]] |
||
| genre |
| genre = [[Computer cluster#Cluster management|Cluster management software]] |
||
| license |
| license = [[Apache License 2.0]] |
||
⚫ | |||
}} |
}} |
||
⚫ | |||
⚫ | |||
==History== |
==History== |
||
Mesos began as a research project in the UC Berkeley RAD Lab by then PhD students Benjamin Hindman, Andy Konwinski, and [[Matei Zaharia]], as well as professor [[Ion Stoica]]. The students started working on the project as part of a course taught by [[David Culler]]. It was originally named ''Nexus'' but due to a conflict with another university's project, was renamed to Mesos.<ref name="hug-meetup">{{cite web|last1=Zaharia|first1=Matei|title=HUG Meetup August 2010: Mesos: A Flexible Cluster Resource manager - Part 1|url=https://www.youtube.com/watch?v=lE3jR6nM3bw|website=youtube.com|accessdate=13 January 2015}}</ref> |
Mesos began as a research project in the UC Berkeley RAD Lab by then PhD students Benjamin Hindman, Andy Konwinski, and [[Matei Zaharia]], as well as professor [[Ion Stoica]]. The students started working on the project as part of a course taught by [[David Culler]]. It was originally named ''Nexus'' but due to a conflict with another university's project, was renamed to Mesos.<ref name="hug-meetup">{{cite web|last1=Zaharia|first1=Matei|title=HUG Meetup August 2010: Mesos: A Flexible Cluster Resource manager - Part 1|url=https://www.youtube.com/watch?v=lE3jR6nM3bw|website=youtube.com|accessdate=13 January 2015}}</ref> |
||
Mesos was first presented in 2009 (while still named Nexus) by Andy Konwinski at HotCloud '09 in a talk accompanying the first paper published about the project.<ref> |
Mesos was first presented in 2009 (while still named Nexus) by Andy Konwinski at HotCloud '09 in a talk accompanying the first paper published about the project.<ref>{{Cite web|url=http://usenix.org/event/hotcloud09/tech/full_papers/hindman.pdf|title=A Common Substrate for Cluster Computing}}</ref> Later in 2011 it was presented in a more mature state in a talk by Zaharia at the [[Usenix]] Symposium on Networked Systems Design and Implementation conference about the paper "Mesos: A Platform for Fine-Grained Resource Sharing in the Data Center" by Benjamin Hindman, Andy Konwinski, Zaharia, [[Ali Ghodsi]], Anthony D. Joseph, [[Randy Katz]], [[Scott Shenker]], [[Ion Stoica]].<ref name="mesos-paper">{{cite journal|last1=Hindman|first1=Benjamin|last2=Konwinski|first2=Andy|last3=Zaharia|first3=Matei|last4=Ghodsi|first4=Ali|last5=Joseph|first5=Anthony|last6=Katz|first6=Randy|last7=Shenker|first7=Scott|last8=Stoica|first8=Ion|title=Mesos: A Platform for Fine-Grained Resource Sharing in the Data Center|journal=NSDI|date=2011|volume=11|page=22-22|url=http://people.csail.mit.edu/matei/papers/2011/nsdi_mesos.pdf|accessdate=12 January 2015}}</ref> |
||
On July 27, 2016, the [[Apache Software Foundation]] announced version 1.<ref>{{Cite news |title= The Apache Software Foundation Announces Apache Mesos v1.0 |work= Press release |date= July 27, 2016 |url= https://blogs.apache.org/foundation/entry/the_apache_software_foundation_announces97 |access-date= February 24, 2017 }}</ref> It added the ability to centrally supply [[Docker (software)|Docker]], [[CoreOS|rkt]] and appc instances.<ref> |
On July 27, 2016, the [[Apache Software Foundation]] announced version 1.<ref>{{Cite news |title= The Apache Software Foundation Announces Apache Mesos v1.0 |work= Press release |date= July 27, 2016 |url= https://blogs.apache.org/foundation/entry/the_apache_software_foundation_announces97 |access-date= February 24, 2017 }}</ref> It added the ability to centrally supply [[Docker (software)|Docker]], [[CoreOS|rkt]] and [[CoreOS|appc]] instances.<ref>{{Cite web|url=https://siliconangle.com/2016/07/27/mesos-1-0-brings-a-new-container-runtime-and-more-third-party-integrations/|title=Mesos 1.0 brings a new container runtime and more third party integrations|date=July 27, 2016}}</ref> |
||
On April 5, 2021, it was voted to move Mesos to the Apache Attic,<ref>{{Cite web|title=[VOTE] Move Apache Mesos to Attic|url=https://lists.apache.org/x/thread.html/rab2a820507f7c846e54a847398ab20f47698ec5bce0c8e182bfe51ba@%3Cdev.mesos.apache.org%3E|url-status=live|access-date=2021-04-07|website=lists.apache.org|archive-url=https://web.archive.org/web/20210406081248/https://lists.apache.org/x/thread.html/rab2a820507f7c846e54a847398ab20f47698ec5bce0c8e182bfe51ba@%3Cdev.mesos.apache.org%3E |archive-date=2021-04-06 }}</ref> however the vote was cancelled two days later due to increased interest.<ref>{{Cite web|title=Re: [VOTE] Move Apache Mesos to Attic|url=https://lists.apache.org/thread.html/rf0359da13d1c3baff88283310413d4287c4ba45a878f2c98b5955c0f%40%3Cdev.mesos.apache.org%3E|url-status=live|access-date=2021-04-09|website=lists.apache.org|archive-url=https://web.archive.org/web/20210409085629/https://lists.apache.org/thread.html/rf0359da13d1c3baff88283310413d4287c4ba45a878f2c98b5955c0f@%3Cdev.mesos.apache.org%3E |archive-date=2021-04-09 }}</ref> |
|||
==Technology== |
==Technology== |
||
⚫ | Mesos uses Linux [[cgroups]] to provide isolation for [[CPU]], [[Virtual memory|memory]], [[I/O]] and [[file system]].<ref name="isolation">{{cite web|title=Open-Source Datacenter Computing with Apache Mesos|url=https://opensource.com/business/14/9/open-source-datacenter-computing-apache-mesos|first=Sachin P.|last=Bappalige|website=[[Red Hat#Opensource.com|OpenSource.com]]|publisher=[[Red Hat]]|date=2014-09-15|accessdate=2016-12-10}}</ref> |
||
⚫ | |||
⚫ | Mesos uses Linux [[ |
||
⚫ | |||
⚫ | |||
| name = Apache Aurora |
|||
| logo = [[File:Apache_Aurora_Logo.svg|250px|Apache Aurora logo]] |
|||
| developer = [[Apache Software Foundation]] |
|||
| discontinued = Yes |
|||
| latest release version = 0.22.0 |
|||
| latest release date = {{Start date and age|2019|12|12}}<ref>{{cite web|url=https://aurora.apache.org/blog/|title=Apache Aurora Blog|access-date=16 March 2021}}</ref> |
|||
| repo = {{URL|https://gitbox.apache.org/repos/asf?p%3Daurora.git|Aurora Repository}} |
|||
| programming language = [[Java (programming language)|Java]], [[Python (programming language)|Python]] |
|||
| genre = Mesos Framework |
|||
| license = [[Apache License 2.0]] |
|||
⚫ | |||
}} |
|||
===Apache Aurora=== |
===Apache Aurora=== |
||
Apache Aurora is a Mesos framework for both long-running services and cron jobs, originally developed by Twitter starting in 2010 and open sourced in late 2013.<ref>{{cite web|title=All about Apache Aurora|url=https://blog.twitter.com/2015/all-about-apache-aurora|publisher=[[Twitter]]|accessdate=20 May 2015}}</ref> It can scale to tens of thousands of servers, and holds many similarities to |
Apache Aurora is a Mesos framework for both long-running services and cron jobs, originally developed by Twitter starting in 2010 and open sourced in late 2013.<ref>{{cite web|title=All about Apache Aurora|url=https://blog.twitter.com/2015/all-about-apache-aurora|publisher=[[Twitter]]|accessdate=20 May 2015}}</ref> It can scale to tens of thousands of servers, and holds many similarities to Borg<ref>{{cite web|title=Large-scale cluster management at Google with Borg|url=http://static.googleusercontent.com/media/research.google.com/en/us/pubs/archive/43438.pdf|accessdate=20 May 2015}}</ref><ref>{{cite web|title=Twitter's Aurora and How It Relates to Google's Borg|date=18 February 2015 |url=http://thenewstack.io/twitters-aurora-relates-googles-borg-part-1/|accessdate=20 May 2015}}</ref> including its rich [[domain-specific language]] (DSL) for configuring services. As of February 2020 the project was retired to the Attic.<ref>{{Cite web|title=Apache Aurora - Apache Attic|url=https://attic.apache.org/projects/aurora.html|access-date=2021-02-18|website=attic.apache.org}}</ref> A fork of the project was maintained by former members, hosted on GitHub under the name Aurora Scheduler.<ref>{{Cite web|title=Aurora Scheduler|url=https://github.com/aurora-scheduler|access-date=2023-04-02|website=GitHub|language=en}}</ref> |
||
===Chronos=== |
===Chronos=== |
||
Chronos is a distributed cron-like system |
Chronos is a distributed cron-like system which is elastic and capable of expressing dependencies between jobs.<ref>{{cite web|title=Chronos|url=https://github.com/mesos/chronos|website=GitHub.com|publisher=[[GitHub]]|accessdate=30 March 2015}}</ref> |
||
===Marathon=== |
===Marathon=== |
||
Marathon is promoted for [[platform as a service]] or container orchestration system scaling to thousands of physical servers. It is fully [[REST]] |
Marathon is promoted for [[platform as a service]] or [[Container (virtualization)|container]] [[Orchestration (computing)|orchestration]] system scaling to thousands of physical servers. It is fully [[REST]]-based and allows [[Feature toggle#Canary release|canary-style deployment]]s and deployment topologies. It is written in the programming language [[Scala (programming language)|Scala]].<ref>{{cite web|title=Marathon|url=https://mesosphere.github.io/marathon/|website=Mesosphere.GitHub.io|publisher=[[Mesosphere (software)|Mesosphere]]|date=2014|accessdate=30 March 2015}}</ref> |
||
==Users== |
==Users== |
||
The social networking site Twitter began using Mesos and Apache Aurora in 2010, after Hindman gave a presentation to a group of Twitter engineers.<ref name="wired-mesos-borg">{{cite magazine|last1=Metz|first1=Cade|title=Return of the Borg: How Twitter Rebuilt Google's Secret Weapon|url=https://www.wired.com/2013/03/google-borg-twitter-mesos/|magazine=Wired|accessdate=12 January 2015}}</ref> |
|||
Airbnb said in July 2013 that it uses Mesos to run data processing systems like [[Apache Hadoop]] and [[Apache Spark]].<ref>{{cite web|last1=Harris|first1=Derrick|title=Airbnb is engineering itself into a data-driven company|url=https://gigaom.com/2013/07/29/airbnb-is-engineering-itself-into-a-data-driven-company/|website=gigaom.com|accessdate=12 January 2015}}</ref> |
Airbnb said in July 2013 that it uses Mesos to run data processing systems like [[Apache Hadoop]] and [[Apache Spark]].<ref>{{cite web|last1=Harris|first1=Derrick|title=Airbnb is engineering itself into a data-driven company|url=https://gigaom.com/2013/07/29/airbnb-is-engineering-itself-into-a-data-driven-company/|website=gigaom.com|accessdate=12 January 2015}}</ref> |
||
The Internet auction website [[eBay]] stated in April 2014 that it used Mesos to run [[continuous integration]] on a per-developer basis. They accomplish this by using a custom Mesos plugin that allows developers to launch their own private [[Jenkins (software)|Jenkins]] instance.<ref>{{cite web|last1=The eBay PAAS Team|title=Delivering |
The Internet auction website [[eBay]] stated in April 2014 that it used Mesos to run [[continuous integration]] on a per-developer basis. They accomplish this by using a custom Mesos plugin that allows developers to launch their own private [[Jenkins (software)|Jenkins]] instance.<ref>{{cite web|last1=The eBay PAAS Team|title=Delivering eBay's CI Solution with Apache Mesos - Part I|url=http://www.ebaytechblog.com/2014/04/04/delivering-ebays-ci-solution-with-apache-mesos-part-i/|website=EbayTechBlog.com|date=4 April 2014 |publisher=eBay|accessdate=12 January 2015}}</ref> |
||
In April 2015, it was announced that [[Apple Inc.|Apple]] service [[Siri]] is using its own Mesos framework called Jarvis.<ref>{{cite web|last=Harris|first=Derrick|title=Apple Details How It Rebuilt Siri on Mesos|url=https://mesosphere.com/blog/2015/04/23/apple-details-j-a-r-v-i-s-the-mesos-framework-that-runs-siri/|website=Mesosphere.com|publisher=Mesosphere|date=2015-04-23|accessdate=2015-04-27}}</ref> |
In April 2015, it was announced that [[Apple Inc.|Apple]] service [[Siri]] is using its own Mesos framework called Jarvis.<ref>{{cite web|last=Harris|first=Derrick|title=Apple Details How It Rebuilt Siri on Mesos|url=https://mesosphere.com/blog/2015/04/23/apple-details-j-a-r-v-i-s-the-mesos-framework-that-runs-siri/|website=Mesosphere.com|publisher=Mesosphere|date=2015-04-23|accessdate=2015-04-27|archive-url=https://web.archive.org/web/20150429225603/https://mesosphere.com/blog/2015/04/23/apple-details-j-a-r-v-i-s-the-mesos-framework-that-runs-siri/|archive-date=2015-04-29|url-status=dead}}</ref> |
||
In August 2015, it was announced that [[Verizon]] selected Mesosphere's DC/OS, which is based on open source Apache Mesos, for data center service orchestration.<ref>{{cite web|title=Verizon selects Mesosphere DCOS as nationwide platform for data center service orchestration |
In August 2015, it was announced that [[Verizon]] selected Mesosphere's DC/OS, which is based on open source Apache Mesos, for data center service orchestration.<ref>{{cite web|title=Verizon selects Mesosphere DCOS as nationwide platform for data center service orchestration |
||
|url=http://www.verizon.com/about/news/verizon-selects-mesosphere-dcos-nationwide-platform-data-center-service-orchestration|publisher=Verizon|accessdate=21 August 2015}}</ref> |
|date=21 August 2015 |url=http://www.verizon.com/about/news/verizon-selects-mesosphere-dcos-nationwide-platform-data-center-service-orchestration|publisher=Verizon|accessdate=21 August 2015}}</ref> |
||
In November 2015, [[Yelp]] announced they had been using Mesos and Marathon for a year and a half for production services.<ref>{{Cite web|url=http://engineeringblog.yelp.com/2015/11/introducing-paasta-an-open-platform-as-a-service.html|title=Introducing PaaSTA: An Open, Distributed, Platform as a Service|website=engineeringblog.yelp.com|access-date=2016-07-12}}</ref> |
In November 2015, [[Yelp]] announced they had been using Mesos and Marathon for a year and a half for production services.<ref>{{Cite web|url=http://engineeringblog.yelp.com/2015/11/introducing-paasta-an-open-platform-as-a-service.html|title=Introducing PaaSTA: An Open, Distributed, Platform as a Service|website=engineeringblog.yelp.com|access-date=2016-07-12}}</ref> |
||
==Commercial support== |
==Commercial support== |
||
Software startup |
Software startup Mesosphere, Inc. sells the Datacenter Operating System, a [[distributed operating system]], based on Apache Mesos.<ref name="mesosphere-product">{{cite web|title=The Mesosphere DCOS|url=http://mesosphere.com/product/|website=mesosphere.com|accessdate=13 January 2015}}</ref> In September 2015, [[Microsoft]] announced a commercial partnership with Mesosphere to build container scheduling and orchestration services for [[Microsoft Azure]].<ref>{{cite web|url=https://www.zdnet.com/article/new-azure-container-service-to-bring-together-mesos-docker-and-azure-cloud/|title=New Azure Container Service to bring together Mesos, Docker and Azure cloud|author=Mary Jo Foley|author-link=Mary Jo Foley|work=[[ZDNet]]|date=September 29, 2015}}</ref> In October 2015, [[Oracle Corporation|Oracle]] announced support for Mesos through [[Oracle Cloud|Oracle Container Cloud Service]].<ref>{{Cite web|url=https://www.oracle.com/corporate/pressrelease/iaas-102715.html|title=Oracle Updates Oracle Cloud Infrastructure Services|website=oracle.com|language=en-US|access-date=2018-02-06}}</ref> |
||
==See also== |
|||
{{Portal|Free and open-source software}} |
|||
* [[Dominant resource fairness]] - the resource-sharing policy used in Mesos. |
|||
* [[List of cluster management software]] |
|||
* [[Comparison of cluster software]] |
|||
==References== |
==References== |
||
Line 57: | Line 77: | ||
==External links== |
==External links== |
||
⚫ | |||
⚫ | |||
⚫ | |||
* [https://mesosphere.com/ Mesosphere] |
|||
{{Apache Software Foundation}} |
|||
{{Linux |
{{Linux containers}} |
||
[[Category:Apache Software Foundation projects|Mesos]] |
[[Category:Apache Software Foundation projects|Mesos]] |
||
Line 67: | Line 86: | ||
[[Category:Cloud infrastructure]] |
[[Category:Cloud infrastructure]] |
||
[[Category:Free software for cloud computing]] |
[[Category:Free software for cloud computing]] |
||
[[Category:Linux |
[[Category:Linux containerization]] |
||
[[Category:Software using the Apache license]] |
[[Category:Software using the Apache license]] |
Latest revision as of 01:23, 21 October 2024
Developer(s) | Apache Software Foundation |
---|---|
Stable release | 1.11.0
/ November 24, 2020[1] |
Repository | Mesos Repository |
Written in | C++ |
Type | Cluster management software |
License | Apache License 2.0 |
Website | mesos |
Apache Mesos is an open-source project to manage computer clusters. It was developed at the University of California, Berkeley.
History
[edit]Mesos began as a research project in the UC Berkeley RAD Lab by then PhD students Benjamin Hindman, Andy Konwinski, and Matei Zaharia, as well as professor Ion Stoica. The students started working on the project as part of a course taught by David Culler. It was originally named Nexus but due to a conflict with another university's project, was renamed to Mesos.[2]
Mesos was first presented in 2009 (while still named Nexus) by Andy Konwinski at HotCloud '09 in a talk accompanying the first paper published about the project.[3] Later in 2011 it was presented in a more mature state in a talk by Zaharia at the Usenix Symposium on Networked Systems Design and Implementation conference about the paper "Mesos: A Platform for Fine-Grained Resource Sharing in the Data Center" by Benjamin Hindman, Andy Konwinski, Zaharia, Ali Ghodsi, Anthony D. Joseph, Randy Katz, Scott Shenker, Ion Stoica.[4]
On July 27, 2016, the Apache Software Foundation announced version 1.[5] It added the ability to centrally supply Docker, rkt and appc instances.[6]
On April 5, 2021, it was voted to move Mesos to the Apache Attic,[7] however the vote was cancelled two days later due to increased interest.[8]
Technology
[edit]Mesos uses Linux cgroups to provide isolation for CPU, memory, I/O and file system.[9] Mesos is comparable to Google's Borg scheduler, a platform used internally to manage and distribute Google's services.[10]
Developer(s) | Apache Software Foundation |
---|---|
Final release | 0.22.0
/ December 12, 2019[11] |
Repository | Aurora Repository |
Written in | Java, Python |
Type | Mesos Framework |
License | Apache License 2.0 |
Website | aurora |
Apache Aurora
[edit]Apache Aurora is a Mesos framework for both long-running services and cron jobs, originally developed by Twitter starting in 2010 and open sourced in late 2013.[12] It can scale to tens of thousands of servers, and holds many similarities to Borg[13][14] including its rich domain-specific language (DSL) for configuring services. As of February 2020 the project was retired to the Attic.[15] A fork of the project was maintained by former members, hosted on GitHub under the name Aurora Scheduler.[16]
Chronos
[edit]Chronos is a distributed cron-like system which is elastic and capable of expressing dependencies between jobs.[17]
Marathon
[edit]Marathon is promoted for platform as a service or container orchestration system scaling to thousands of physical servers. It is fully REST-based and allows canary-style deployments and deployment topologies. It is written in the programming language Scala.[18]
Users
[edit]The social networking site Twitter began using Mesos and Apache Aurora in 2010, after Hindman gave a presentation to a group of Twitter engineers.[10]
Airbnb said in July 2013 that it uses Mesos to run data processing systems like Apache Hadoop and Apache Spark.[19]
The Internet auction website eBay stated in April 2014 that it used Mesos to run continuous integration on a per-developer basis. They accomplish this by using a custom Mesos plugin that allows developers to launch their own private Jenkins instance.[20]
In April 2015, it was announced that Apple service Siri is using its own Mesos framework called Jarvis.[21]
In August 2015, it was announced that Verizon selected Mesosphere's DC/OS, which is based on open source Apache Mesos, for data center service orchestration.[22]
In November 2015, Yelp announced they had been using Mesos and Marathon for a year and a half for production services.[23]
Commercial support
[edit]Software startup Mesosphere, Inc. sells the Datacenter Operating System, a distributed operating system, based on Apache Mesos.[24] In September 2015, Microsoft announced a commercial partnership with Mesosphere to build container scheduling and orchestration services for Microsoft Azure.[25] In October 2015, Oracle announced support for Mesos through Oracle Container Cloud Service.[26]
See also
[edit]- Dominant resource fairness - the resource-sharing policy used in Mesos.
- List of cluster management software
- Comparison of cluster software
References
[edit]- ^ "ASF Git Repos - mesos.git/tag". Retrieved 27 September 2022.
- ^ Zaharia, Matei. "HUG Meetup August 2010: Mesos: A Flexible Cluster Resource manager - Part 1". youtube.com. Retrieved 13 January 2015.
- ^ "A Common Substrate for Cluster Computing" (PDF).
- ^ Hindman, Benjamin; Konwinski, Andy; Zaharia, Matei; Ghodsi, Ali; Joseph, Anthony; Katz, Randy; Shenker, Scott; Stoica, Ion (2011). "Mesos: A Platform for Fine-Grained Resource Sharing in the Data Center" (PDF). NSDI. 11: 22-22. Retrieved 12 January 2015.
- ^ "The Apache Software Foundation Announces Apache Mesos v1.0". Press release. July 27, 2016. Retrieved February 24, 2017.
- ^ "Mesos 1.0 brings a new container runtime and more third party integrations". July 27, 2016.
- ^ "[VOTE] Move Apache Mesos to Attic". lists.apache.org. Archived from the original on 2021-04-06. Retrieved 2021-04-07.
- ^ "Re: [VOTE] Move Apache Mesos to Attic". lists.apache.org. Archived from the original on 2021-04-09. Retrieved 2021-04-09.
- ^ Bappalige, Sachin P. (2014-09-15). "Open-Source Datacenter Computing with Apache Mesos". OpenSource.com. Red Hat. Retrieved 2016-12-10.
- ^ a b Metz, Cade. "Return of the Borg: How Twitter Rebuilt Google's Secret Weapon". Wired. Retrieved 12 January 2015.
- ^ "Apache Aurora Blog". Retrieved 16 March 2021.
- ^ "All about Apache Aurora". Twitter. Retrieved 20 May 2015.
- ^ "Large-scale cluster management at Google with Borg" (PDF). Retrieved 20 May 2015.
- ^ "Twitter's Aurora and How It Relates to Google's Borg". 18 February 2015. Retrieved 20 May 2015.
- ^ "Apache Aurora - Apache Attic". attic.apache.org. Retrieved 2021-02-18.
- ^ "Aurora Scheduler". GitHub. Retrieved 2023-04-02.
- ^ "Chronos". GitHub.com. GitHub. Retrieved 30 March 2015.
- ^ "Marathon". Mesosphere.GitHub.io. Mesosphere. 2014. Retrieved 30 March 2015.
- ^ Harris, Derrick. "Airbnb is engineering itself into a data-driven company". gigaom.com. Retrieved 12 January 2015.
- ^ The eBay PAAS Team (4 April 2014). "Delivering eBay's CI Solution with Apache Mesos - Part I". EbayTechBlog.com. eBay. Retrieved 12 January 2015.
- ^ Harris, Derrick (2015-04-23). "Apple Details How It Rebuilt Siri on Mesos". Mesosphere.com. Mesosphere. Archived from the original on 2015-04-29. Retrieved 2015-04-27.
- ^ "Verizon selects Mesosphere DCOS as nationwide platform for data center service orchestration". Verizon. 21 August 2015. Retrieved 21 August 2015.
- ^ "Introducing PaaSTA: An Open, Distributed, Platform as a Service". engineeringblog.yelp.com. Retrieved 2016-07-12.
- ^ "The Mesosphere DCOS". mesosphere.com. Retrieved 13 January 2015.
- ^ Mary Jo Foley (September 29, 2015). "New Azure Container Service to bring together Mesos, Docker and Azure cloud". ZDNet.
- ^ "Oracle Updates Oracle Cloud Infrastructure Services". oracle.com. Retrieved 2018-02-06.