SATURN2015

Software architects tend to think in terms of "code complete." But  "code complete" is not "code in production." There are potentially long delays between the time that code is complete and the time that code is placed into production. These delays are caused by the necessity for coordination among all of the various stakeholders to achieve consistency in both the developed code and the supporting technologies and libraries.

DevOps is a set of practices intended to reduce the time between committing a change to a system and placing that change into normal production, while ensuring high quality. That is, the goal of DevOps is to reduce the time between code complete and code in production. One important technique is to have a tool chain that automatically places code into production after a commit. This is called continuous deployment. Continuous deployment is most effective when coupled with the use of a microservice architecture.

In this session, three experts in DevOps will lead you through a discussion of "What is DevOps?" "What is continuous deployment?" and "What is microservice architecture?" You will come away not only with an appreciation of the reasons for the time between code complete and code in production but also with a collection of techniques that will enable you to reduce that time in your organization.

Invited Talk: Principles of Microservices

Sam Newman discusses the buzz that we have seen around microservices over the last year and explains that there has often been a lack of clarity as to what microservices are or how to implement them well. I've been working to distill the principles of microservices to help ensure that we don't just end up repeating the mistakes we made during the last 20 years of service-oriented architecture.

I'll talk about the history of where microservices came from, what they are, the benefits and downsides, and the core principles to stick to in order to do to them well.