The talk focuses on architectural changes and new tools we should adopt to be able to tackle the problems presented by a demand for modern, responsive, fault tolerant and elastic systems. It is based on the material published in The DevOps 2.1 Toolkit: Building, testing, deploying, and monitoring services inside Docker Swarm clusters.
The talk will go through the whole microservices development lifecycle. We’ll start from the very beginning and define and design architecture. From there on we’ll move from requirements, technological choices and development environment setup, through coding and testing all the way until the final deployment to production. We won’t stop there. Once our new services are up and running we’ll see how to maintain them, scale them depending on resource utilization and response time, and recover them in case of failures. We’ll try to balance the need for creative manual work and the need to automate as much of the process as possible.
The goal is to design a fully automated continuous deployment (CDP) pipeline. We’ll see how microservices fit into CDP and immutable containers concepts and why the best results are obtained when those three are combined into one unique framework.


Comments are closed.

Alberto Varela at 19:10 on 7 Oct 2017

Good talk! Maybe a bit fast, but nice in overall, good job!

Mike at 20:59 on 7 Oct 2017

Excellent talk, with good demonstration.

Muy bien aprovechado el tiempo. Interesante demo para la parte práctica y aunque a gran velocidad puntos muy importantes acerca de qué es y por qué es imprescindible una cultura DevOps... Recordemos que solo aportamos valor si esta en producción y alguien lo usa :)

Javier Molina at 13:44 on 9 Oct 2017

Amazing talk, amazing speed and concepts. I really liked the way he presented everything, not only from the theoretical point of view but doing a live demo.

Javi Sánchez at 16:14 on 9 Oct 2017

I liked it. Lots of things I didn't know about docker (e.g. stack deploy) and also nice to see it along with Jenkins stuff. On the other hand, too much content for an hour long talk (there wasn't enough time to explain or see a couple of things working).