Dave’s article on The New Stack shows how engineers can evolve to become serverless-first.
Time to adopt serverless?
So you have made the decision, perhaps at executive level, that your org needs to adopt serverless. Perhaps you are focused servicing the current and future digital needs of your customers. However, you are probably in a similar situation to most orgs. You don’t have the luxury of starting from scratch. And your engineering teams are probably fully deployed in running and maintaining tech that is currently serving your customer base.
So how do you make the change and evolve into serverless. With over twenty years of engineering leadership in the telecoms and financial services industries, Dave’s shares his way forward. It starts by looking at how to evolve your engineering teams for serverless.
The role of serverless engineers
Dave looks at the role of software engineers. And how it has evolved every few years. It is some times based on a fad and other times due to a tech shift in the industry. Either way the role has expanded to engineers building, running and owning tech. This means that they now need to understand tech in its fullest abstraction.
Thankfully, serverless architecture facilitates this new way of work and Fauna have an excellent product to achieve serverless deployment.
Dave looks at serverless concepts such as cloud native, event-driven, less ops/more architecture, the flywheel effect and cognitive burden. He also covers the game-changing effect of the data journey and a low friction developer experience.
Serverless first mindset
He uncovers the serverless first mindset of today’s engineer which is different to the specialist of the past. He also looks towards the future. Some engineering roles are merging eg. data and application engineering captured in the quote from Amazon CTO Werner Vogels:
“The only code you will have to write is business logic.”