“Microservices are the first post DevOps revolution architecture," says Neal Ford, Architect and Meme Wrangler at Thoughtworks.
I had the chance to record a 22 minute interview with him, where he explained to me why the DevOps revolution was a prerequisite for the microservices architectural style to become possible.
This episode, the second in the Thoughtworks Podcast series, is a quick introduction to what microservices are, what kind of architectural principles can be used to implement them, and what a good test strategy for microservices can look like. We also explain why you should have a continuous delivery practice running before starting to develop microservices.
We close with the definition of the term “real virtual machine” - which is the place you need to deploy your microservices to as soon as possible to get early user feedback.
Disclaimer: The statements and opinions expressed in this article are those of the author(s) and do not necessarily reflect the positions of Thoughtworks.
Thoughtworks acknowledges the Traditional Owners of the land where we work and live, and their continued connection to Country. We pay our respects to Elders past and present. Aboriginal and Torres Strait Islander peoples were the world's first scientists, technologists, engineers and mathematicians. We celebrate the stories, culture and traditions of Aboriginal and Torres Strait Islander Elders of all communities who also work and live on this land.
As a company, we invite Thoughtworkers to be actively engaged in advancing reconciliation and strengthen their solidarity with the First Peoples of Australia. Since 2019, we have been working with Reconciliation Australia to formalize our commitment and take meaningful action to advance reconciliation. We invite you to review our Reconciliation Action Plan.