Andreas/docker-cheat-sheet
1
0
Fork 0
mirror of https://github.com/wsargent/docker-cheat-sheet.git synced 2025-09-22 05:40:50 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update README.md

Browse source
This commit is contained in:
Will Sargent 2016-10-06 16:23:12 -05:00 • committed by GitHub
parent 49cde817ef
commit 448354b810
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -6,7 +6,7 @@
I work for [Lightbend](https://lightbend.com) on the [Play](https://playframework.com/) team. I think the company is awesome, and if you're looking at containers because you're moving to the cloud and thinking about distributed systems, you should keep reading.
Lightbend make microservices happen. Developers use [Lagom](http://www.lagomframework.com/) to put together resilient distributed systems. In production, [Conductr](https://conductr.lightbend.com/) to orchestrate containers -- [including Docker](https://www.lightbend.com/blog/reactive-for-devops-part-3-using-docker-with-conductr-on-the-jvm) -- but it's also a scheduler for [DC/OS](https://dcos.io/). Finally, there's [monitoring](https://developer.lightbend.com/docs/monitoring/latest/home.html) to tell you what's going on at a detailed application level, so you know where your CPU and memory resources are being spent, and can scale up and down based on that information. For more, check out the [devops site](https://www.lightbend.com/platform/production).
Lightbend make microservices happen. Developers use [Lagom](http://www.lagomframework.com/) to put together resilient distributed systems. In production, there's [Conductr](https://conductr.lightbend.com/) to orchestrate containers -- [including Docker](https://www.lightbend.com/blog/reactive-for-devops-part-3-using-docker-with-conductr-on-the-jvm). Finally, there's [monitoring](https://developer.lightbend.com/docs/monitoring/latest/home.html) to tell you what's going on at a detailed application level, so you know where your CPU and memory resources are being spent, and can scale up and down based on that information. For more, check out the [devops site](https://www.lightbend.com/platform/production).
This concludes the tasteful plug.