3 ms·
> Serverless is still many years away I strongly disagree, yes it is early and some of the tools notably debugging and logs aren't anywhere near the level they
by rmason 9y ago
> Serverless is still many years away
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.
- electricEmu 9y ago> I'm developing an app with serverless 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.
- georgebarnett 9y agoYou disagree, yet readily admit the toolchain is lacking. 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.