Member-only story
Why Serverless Teams Should Embrace Continuous Refactoring
Stay afresh in serverless
Serverless adoption brings promises to many organizations! Promises of cost efficiency, engineering efficiency, and business efficiency. However, serverless is not a technology that, once successfully adopted, can be left unattended to rust.
The motivation to adopt serverless should never be to get the job done and never look back. If you adopt it with this attitude you will inevitably get into the legacy migration juggernaut that will haunt you much sooner than you anticipated.
Why is this so?
Evolving Ecosystem
The serverless ecosystem is constantly evolving. At times, this evolution is so fast that teams can find it hard to keep up. Often, it can feel like the force of a mighty procession, marching faster and gaining strength at every step. The challenge is to be part of it and somehow keep up with the relentless pace rather than being a bystander.
You might be now thinking with a raised eyebrow and a mischievous smile, what’s so great with this modern technology that demands so much from you and make you run alongside all the time? Isn’t this counter-productive? Isn’t this a disruptive development practice?
The simple answer to such questions is, it depends:
- on your serverless mindset
- on how agile your team is
- on your faith in incremental and iterative development
- on how fresh you want to stay with serverless
- on whether or not you want to protect your tech investments
- on whether or not you want to retain your best engineers
- on your business’s acceleration ambitions
- on the services you offer to your customers
- on how much you care about your customers
Yes, it depends!
Serverless requires a new way of thinking, a new way of working, and a new way of running applications. Meaning, we need to change our way of thinking, our way of working…
