Embrace the Creative Disruption of Cloud Native / Serverless

John Gilbert
Nov 9 · 2 min read

Simply put, Cloud Native with Serverless is just different. It turns many widely held practices and assumptions on their heads. This can be disconcerting for those of us who have been in this industry for a long time. Grappling with any paradigm shift is painful. We tend to put our hearts and souls into the systems we build. So it is hard to let go when things change. But that is exactly what has happened. The cloud and particularly serverless are disrupting forces. They have changed all the rules and all the assumptions.

It was helpful for me to come to terms with the fact that there was nothing wrong with the way we used to build systems. Our architecture was highly tuned for the world it lived in. It was a world of long lead times (i.e. long procurement cycles and quarterly releases).

When we moved into the cloud we came to realize that our architecture did not fit in this new world of short lead times. There was an impedance mismatch. Like trying to fit a square peg in a round hole. We could continue on against the grain or we could adapt. It was a hard choice, but an obvious one.

On new years eve of 2016 I was glad that 2015 was behind me. It had been a painful process of unlearning and rewiring my software engineering brain. But I was starting to see the potential and I was excited about the road ahead. And it was fun! I was having more fun then ever in my long career. This was in large part due to the peace of mind that came with the serverless approach, with regard to all the ilities, and the hard lessons that led to the autonomous services approach I talk so much about.

There is no shame in changing course. The past is the past. Embrace the disruption. And be prepared to have fun! Lots of fun!!


For more thoughts on serverless and cloud-native checkout the other postings in this series and my books: Cloud Native Development Patterns and Best Practices and JavaScript Cloud Native Development Cookbook.