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:19:05 -05:00 • committed by GitHub
parent c393a71764
commit 860c44cefe
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -6,9 +6,9 @@
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, using [Lagom](http://www.lagomframework.com/) to put together resilient distributed systems, [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) -- (it's also a scheduler for [DC/OS](https://dcos.io/) among other things) and [Monitoring](https://developer.lightbend.com/docs/monitoring/latest/home.html) to tell you what's going on at a detailed application level, so you have application level information and know where your CPU and memory resources are being spent, and can scale up and down based on that information.
Lightbend make microservices happen, using [Lagom](http://www.lagomframework.com/) to put together resilient distributed systems, [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) -- (it's also a scheduler for [DC/OS](https://dcos.io/) among other things) and [Monitoring](https://developer.lightbend.com/docs/monitoring/latest/home.html) to tell you what's going on at a detailed application level, so you have application level information and 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).
For more, check out the [devops site](https://www.lightbend.com/platform/production).
This concludes the tasteful plug.
## Table of Contents