Work at Docker Inc. Ex Serverless.com. Ruby, Golang, API Aficionado, Serverless, Docker, Mesosphere. Asst. Scoutmaster at BSA Troop 39. Amateur Photographer. Entrepreneur.
Writing Serverless is time consuming compared to a monolith of the same language
Learning to write code to a completely new environment
It is the same runtime on the FaaS provider. The environment has restrictions but it is the same runtime. No new learnings.
Maintenance
Serverless needs a lot of maintenance compared to a crud app. Versioning and constant updates requiring a lot of time consuming
I respectfully disagree. Its the perspective I guess. Maintaining a lot of functions which do one and only thing or one huge blob of monolith that does a lot. If you are worried about maintainace, please give Serverless Framework (serverless.com/framework/) a try. It will not disappoint you.
AWS Lambda may be cheap . But API Gateway is not .
Compared to maintaining a fleet of infrastructure? And the team of devops that have to keep an eye on it to keep it up, patched and running?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I wouldn't use a CRUD app in serverless
Reasons
Learning to write code to a completely new environment
Serverless needs a lot of maintenance compared to a crud app. Versioning and constant updates requiring a lot of time consuming
AWS Lambda may be cheap . But API Gateway is not .
If you think about google functions , they are still in beta
Other options would be IBM Open whisk or Azure functions
These are my opinions about serverless apps .
You can still use it if you like . But I wouldn't do it for a simple crud app
It is the same runtime on the FaaS provider. The environment has restrictions but it is the same runtime. No new learnings.
I respectfully disagree. Its the perspective I guess. Maintaining a lot of functions which do one and only thing or one huge blob of monolith that does a lot. If you are worried about maintainace, please give Serverless Framework (serverless.com/framework/) a try. It will not disappoint you.
Compared to maintaining a fleet of infrastructure? And the team of devops that have to keep an eye on it to keep it up, patched and running?