Andreas/docker-cheat-sheet
1
0
Fork 0
mirror of https://github.com/wsargent/docker-cheat-sheet.git synced 2025-12-16 15:10:12 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Remove tasteful plug

Browse source
This commit is contained in:
Will Sargent 2017-07-18 13:50:14 -07:00 • committed by GitHub
parent b325798014
commit d2a1ec5ea2
1 changed files with 0 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

8
README.md
View file

@ -2,14 +2,6 @@
**Want to improve this cheat sheet? See the [Contributing](#contributing) section!**
## A Tasteful Plug for Lightbend
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 ("chaos monkey resistant") microservices. In production, there's [Conductr](https://conductr.lightbend.com/) to [orchestrate](http://www.cakesolutions.net/teamblogs/typesafe-conductr-the-missing-glue-between-dev-and-ops) 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.
## Table of Contents
* [Why Docker](#why-docker)