I'm all for moving forward and using new stuff if it makes my life better, but from the looks of it, Serverless is still many years away before discussions like that can even take place.
I'm all for moving forward and using new stuff if it makes my life better, but from the looks of it, Serverless is still many years away before discussions like that can even take place.
I strongly disagree, yes it is early and some of the tools notably debugging and logs aren't anywhere near the level they need to be.
I'm developing an app with serverless and this article really resonated with me about my struggles. I think once Aurora Serverless launches allowing developers who need a relational database to easily move on the platform you will see rapid growth with serverless.
Why? Because it makes so much sense. Why worry about managing servers or scaling? Why continually write the same boilerplate glue code over and over again?
I know that I'd rather write a configuration file calling best of the best components over writing code. Don't get me wrong I like writing code but I'd rather concentrate on the business logic.
Lambda? If so, what benefit do you see over running AWS Container Service?
I ask because I've tried both. Serverless frameworks (AWS Lambda/AzFunc) were horrific. I picked up Docker as an answer and never looked back.
Others in my company are abandoning serverless after seeing our success. Turns out being easily able to run things locally, very similar to production, is very important. We have no problem concentrating on the business logic AND keeping flexibility.
I've loved my time with serverless framework and aws lambda.
Parents point is saying exactly that - filling out the toolchain to a meaningful completeness is going to take a couple of years.
This isn’t a ding on Lamdas - just a reality - theres a huge backlog of capabilities to catch up on.
I prefer to use the label "FaaS", because it fits clearly into an existing taxonomy and doesn't spark silly arguments about what is, and what is not, serverless or serverful.
Disclosure: I work for Pivotal on a FaaS project.
This could imply that serverless "just need to improved" to a point is good for most.
I argue will NEVER* be good, not matter what kind of glue we put on top of it.
Because, I think, not matter what you do or how hard you try, is the most complex way to do a software project.
*Never: probably not in the next millenium....