Oh also make breaking changes and depreciations every few weeks without documenting them, take forever to fix npm vulnerabilities and also have heaps of shit that doesn’t work because “race conditions that are too hard to fix”.
Honestly I loved serverless framework and have many fond memories and am eternally thankful for it helping my transition to serverless but no chance in hell I’d start a new project with it. CDK just knocks it out of the park
As someone who works with Serverless and the project, I am sorry to hear you are disappointed. Unfortunately a lot of the issues you mention are a little intertwined; we needed to make breaking changes in order to address the npm vulnerabilities in many cases as the modules we made use of had major version changes themselves to address the security vulnerabilities and violating semver just wasn't option. This would have created even bigger issues for users of the framework.
While we do try to make sure all deprecations we are busy making are documented (https://www.serverless.com/framework/docs/deprecations/) I hear you and will make sure to mention this in our next discussion as something to take a look into. Perhaps we can be clearer for folks where to look for this.
I'd also love to find out more what race conditions you are referring to so we can address them. One of the downsides of being an abstraction layer on top of a cloud vendor is that they change things. In fairness, even the CDK team and pretty much every other serverless application framework has suffered from this, but we work hard to minimise this and support changes as soon as they are made.
Thanks for your candor and openness. If you have anything please feel free to share, or even open an issue on the GitHub: https://github.com/serverless/serverless/issues. We want feedback so we can improve!
I found for a lot of changes the console message that linked to "more information" was just a changelog item on the website with the exact same single line of info as the console. No examples or descriptions on how to migrate. I'm not sure if that's improved recently.
The race conditions were generally around resolving references when generating the CF. There are a few resources (I think Kinesis and EventBridge) that have/had open issues for a long long time that basically said they couldn't be resolved because of the way the CF template was generated. I had to manually resolve them via CLI in my build script and set them as env vars instead of using a direct !Ref which leads to some indirection.
Serverless the company created a great free framework but at some stage, I understand they need to make money in order to keep supporting the free framework. As a user, it felt that a lot of engineering effort was redirected to the paid deployment platform and a lot of issues were slow to be resolved. I fully understand the reality of this decision and don't think think its wrong to focus on paid offerings above free ones, it just caused enough headaches that I learned how to use CDK and never really looked back
5
u/justAnotherRedditors Jul 08 '21
Oh also make breaking changes and depreciations every few weeks without documenting them, take forever to fix npm vulnerabilities and also have heaps of shit that doesn’t work because “race conditions that are too hard to fix”.
Honestly I loved serverless framework and have many fond memories and am eternally thankful for it helping my transition to serverless but no chance in hell I’d start a new project with it. CDK just knocks it out of the park