I believe it's not the developers, but it's actually the serverless thing that is not ready yet.
Look, it's all about the developer experience && economics.
When you tell me that:
I have to signup in AWS ecosystem (though I really love it, but some might not).
Then you tell me I have to use all the tools they provide and switching in the future might not be a choice.
Further, things get even scarier: you can't have this whole serverless thing in a self-hosted solution.
Then you add: your bill follows "pay as you go" pattern, and you cannot have some flat simple pricing for your "simple" apps.
And guess what, building a simple CRUD app might take you days.
Then I would tell you: I DON'T BUY IT and good luck convincing other developers!
BTW, I tried the serverless thing to write a lambda function that creates backups and stores them in S3... that experience sucks.
I ended up writing a simpler solution with cron inside the db container then sending the backup to S3... works just fine and can be tested super easily.
I don't think any framework / app/ system is for everyone. I don't know in what point or what tools you used but with AWS Amplify you can literally create a CRUD app these days in less than half a hour with authentication. Sure, unpolished and you'll need more work, but the basics will be all set!
But no means I'm advocating "all things serverless". My point is serverless is mature but we need understanding how fits with our current mental models and team topologies.
...and there's lterally a page called AWS Serverless Customer Success: aws.amazon.com/serverless/customer... with all sorts of real world successful applications that are built on serverless model
I believe it's not the developers, but it's actually the serverless thing that is not ready yet.
Look, it's all about the
developer experience&&economics.When you tell me that:
Then I would tell you: I DON'T BUY IT and good luck convincing other developers!
BTW, I tried the serverless thing to write a lambda function that creates backups and stores them in S3... that experience sucks.
I ended up writing a simpler solution with cron inside the db container then sending the backup to S3... works just fine and can be tested super easily.
I don't think any framework / app/ system is for everyone. I don't know in what point or what tools you used but with AWS Amplify you can literally create a CRUD app these days in less than half a hour with authentication. Sure, unpolished and you'll need more work, but the basics will be all set!
But no means I'm advocating "all things serverless". My point is serverless is mature but we need understanding how fits with our current mental models and team topologies.
Well, to understand how it fits we will need to see real world successful applications that are built on serverless model.
Would you please point me to any such examples?
Lego Group has adopted with much success: medium.com/lego-engineering/the-po...
...and there's lterally a page called AWS Serverless Customer Success: aws.amazon.com/serverless/customer... with all sorts of real world successful applications that are built on serverless model
Thank you so much!
I will read these and come back 😄
Found another high level use case, BBC: twitter.com/drewfirment/status/137...
Thanks again @ibrahimcesar
I've read the articles and from what I understood Lambda good use cases are for apps that have high/undetermined load.
And they're not for usual apps that we can spin in mins with Heroku.