And why it’s more than just a way of structuring code
Press enter or click to view image in full size
Microservices stumbled into the world of web development with a bang. The topic caused heated debates, endless posts, many comparisons to the monolithic architecture, and even use cases coming from big organizations. However, whenever the topic comes up, developers tend to focus mostly on the technical aspects of the microservices revolution rather than the cultural changes that it sparked. While the technology that grew around it is indeed very cool, I find the cultural changes to be more disruptive.
I was lucky to get onto the bandwagon relatively quickly, around 2014, and I still remember how exciting it was to migrate old monoliths into the new cool and sexy microservices. Like many, I was overly focused on technological aspects to begin with — after all, it was a very exciting time (e.g., Docker had just come around).
However, after a couple of years and despite how much things have changed in terms of technology, I believe that code ownership and feature teams had the biggest impact on how software is developed within organizations that adopted microservices.