DEV Community

Discussion on: Upgrading to Serverless Framework v4: The Why and the How

Collapse
 
leob profile image
leob • • Edited

"I'm not exactly thrilled about upgrading from Serverless Framework v3 to v4" - but, you don't have to - be aware that there's an alternative (see below) ...

Yeah they're pushing users to v4 because they have a "revenue model" with that version, it's in fact (semi)commercial now :-)

Also, they're dramatically expanding the scope with shiny new features (even though they're dropping Google/Azure support, which in my opinion wasn't ever to be taken serious anyway) - I think they're really try to exert some "vendor lock-in" on users :-)

However:

"I'll explain why upgrading to v4 will eventually become a necessity for all of us"

That's not a certainty - there is an "escape hatch":

v3 has been "forked", and there's a community-supported OSS version with pretty serious backing, and with the intention to develop and support/maintain it - here it is:

github.com/oss-serverless/serverless

and an article that I came across:

serverlesscorner.com/switching-to-...

In a nutshell:

  • drop-in replacement for Serverless Framework v3, maintained by community contributors

  • fully compatible with existing Serverless Framework v3 configurations, includes support for recent AWS Lambda runtimes (like Node.js 22 and Python 3.12)

Apart from that, I'm seeing evidence of quite a few people migrating away, to CDK or Terraform - the fact that Serverless is no longer "multi cloud" but AWS-only would only encourage that tendency ...

But, I think that the OSS version which I mentioned is a serious alternative - I would encourage users to "look before you leap", and to be aware there are alternatives - nobody's pushing you to migrate to v4.