Hi Hugh, tell us who you are and what lead you into microservices?

I came across microservices about four years ago, and I liked the concepts almost immediately. At that time, I’d been involved in building what we now monolithic systems for decades.  I was more than ready for something, anything that took some of the pain out of the process. One of the things that I like about microservices and microservice systems is that it forces us to rethink and relearn how to build systems. 


What will you be talking about at Voxxed Days Microservices? 

I’m very excited about this talk. The focus of this talk will be on the evolution of systems architectures. These are interesting times. We are learning the good and the bad of building microservice systems. We are also learning that there are better ways to construct monolithic systems. But it does not stop there. We are now also seeing the fascinating emergence of serverless systems. In this talk, we will be walking through the evolutionary journey. We will look at some of the good and bad patterns that are being used. We will look at the serverless, and then I’m going to stick my neck out and project ourselves a bit into the future and speculate where we are heading.


You mention evolving from a Monolith to Microservices to Serverless. Are their valid scenarios where we could evolve backwards, or even not evolve at all ? 

There is always a need for improvements. Our systems are never and will never be perfect. A real warning sign is that you are in an organization that is unwilling or unable or is struggling to evolve. I’m not saying that we need to dump all of our monoliths and microservices and go screaming to serverless. But we are learning how to build better monoliths, better microservices, and we need to learn how to build serverless systems. And it is not just how we code. It is also how we handle data that needs to evolve. These are all things that I will be covering in the talk. 


Good, see you soon then 


#Microservices #Serverless #EventDriven


My contact information:

Twitter: @mckeeh3