Loading...

Implementing Separation of Concerns with Containers (by Jérôme Petazzoni)

204 views

Loading...

Loading...

Transcript

The interactive transcript could not be loaded.

Loading...

Rating is available when the video has been rented.
This feature is not available right now. Please try again later.
Published on Jul 6, 2015

One of the promises of containers is to offer "separation of concerns" between Devs and Ops. Devs are supposedly able to put their code in containers, run those containers locally, and ship them to the Ops team. When deployed on other platforms (from test to staging to QA to production), those containers will behave exactly the same way as they did in development.

But what should we do when our production platform uses a totally different logging system? How should we implement backups or metrics collection in our production containers, without bloating our development containers? In development, it's easy to use a mechanism like Docker Compose to bring up multiple containers together, but how does that work in production stacks?

Jérôme presents many techniques to answer those questions (and a few more), and show how our application containers can remain simple and lean, yet have all the indispensable bells and whistles that are required to run in stable production environments.
Link to the slides: http://www.slideshare.net/jpetazzo/im...

Loading...

When autoplay is enabled, a suggested video will automatically play next.

Up next


to add this to Watch Later

Add to

Loading playlists...