Mindset, infrastructural and organizational changes to adapt to microservices

Microservices are taking the world by storm and it’s more than just an architecture — in order to fully function, microservices approach needs a transformation in your development teams and total commitment to several best practices. This talk touches on several practical points learnt the hard way.

Microservices are taking the world by storm and it’s more than just an architecture — in order to fully function, microservices approach needs a transformation in your development teams and total commitment to several best practices:

• Change. Change is inevitable. Code, dependencies, deployment and release processes will change.
• DevOps. Developers will own the release and every intermediate step has to be automated and kept in code.
• Eliminating hierarchy within the team and increasing autonomy.

This talk will go into detail on what you need to change in order to properly adopt microservices in terms of mindset, infrastructural and organizational changes as well as the benefits that will be obtained as a result of such changes. The lessons are learnt the hard way and this talk is based on a true story — the transformation of development teams at unu GmbH.

I have been developing distributed applications way before it was called microservices. I am the author of a library backed by state-funded research efforts called cote and I have been talking about this subject for over 3 years in several countries.

I can also present this talk as a tutorial/workshop. If this should be a tutorial (or a workshop), a wifi network that doesn’t block IP multicast or IP broadcast would unlock more interesting applications within the session.

The audience will have a complete picture on what is necessary in order to adopt microservices. It’s not a transformation to happen overnight and this talk will make it clear. This will help them make more informed choices when the time comes for adoption.

A general understanding of software development life-cycle and team dynamics will help. The talk is not extremely technical, so no technological prerequisites here.