12 stages to run containers in production & 4 testing scenarios

Watch Codefresh and Cloud 66 Webinar

If you missed the webinar, click on the link here to find out more about the tips and tricks to run Docker containers in production and review the testing strategies for your deployments.

The webinar covered the following points:

  • Introduction to Codefresh and Cloud 66;
  • Daniël van Gils talks about “Docker Inside/Out: the ‘real’ real-world of stacking containers in production”. This includes 12 stages of the hero journey to run containers in production as well as the examples of how developers really use microservices.
  • Alexei Ledenev talks about “Testing Strategies for Docker Driven Development”. It shows a step-by-step demo for testing scenarios to achieve the ultimate solution. An excellent progression showcase with the benefits and drawbacks for each scenario.

The 12 stages of the Hero journey to containers in production.

First couple stages are very straight forward, you work on your project with the methods that you already know. Then you hear about “containers” at the conference, meetup, blog or hear from your colleague. You see what they can do and it looks magical! :)

  • Slim, remove all the layers that you don’t need;
  • Secure, ensure you have the latest updates and remember to remove all secrets;
  • Speedy, follow best deployment practices and run performance tests;
  • Stable, use version numbers for your Docker files;
  • Set, immutable, don’t put databases or complicated volumes into your containers. You can, but the the technology is still too new.
  • 60% of developers use a monolith containerisation. This is understandable as it is a part of the learning curve.
  • 30% of developers use an API first approach, mainly when dealing with the frontend.
  • 7% of developers split their architecture with the containers. This includes workers, API and background processes etc.
  • and only 3% of developers are truly using the microservices in their projects.

Testing Strategies — how to create a test lifecycle around containers.

Alexei started with listing some of the benefits of using containers, such as portability, speed, configurations, flexibility etc. with a brief description of the Docker architecture components.

  • Demo app: all the tests are based on the simple Rest API server that is written in Golang.
  • Postman — which is the Rest API testing tool with the chrome browser extension.
  • Newman — reads the test scenario fails created by Postman
  • Node.js application

Have more questions?

Check out our help page and learn how to build the image and how to deploy a docker stack with Cloud 66.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Cloud 66

Cloud 66

DevOps-as-a-Service to help developers build, deploy and maintain apps on any Cloud. Sign-up for a free trial by visting: www.cloud66.com