Serverless is all about optimizing utilization
-
-
-
It's about empowering people to think about less things, I think, not optimization.
-
I think a lot of it has to do with cost and only paying for the compute you use.
-
From my experience I don't feel like I have saved much on development or received an improved DX ... but maybe it's too new
-
Are the server savings a dominant source of cost for your application?
-
We're trying this model for two reasons: - quicker scaling based on demand - server utilization We haven't gone to production yet so...
-
I can't speak on actual savings. Only DX so far
- 1 more reply
New conversation -
-
-
Except for the loss of abstraction for things like persistence that's not far off
-
Don't Lambda users usually use Dynamo, S3 or other platform-abstracted storage?
-
I would put those in the realm of platform specific. No use using things like Fog when you're committing to the platform.
-
Right, storage abstraction (s3, not SSDs) is a framework concern and the framework was moved into the platform.
End of conversation
New conversation -
-
-
I’ve described it to people as “like Heroku for single controller actions or single Sidekiq workers”.
-
Yeah that sounds right.
End of conversation
New conversation -
-
-
To me "serverless" means "someone else's servers" ;)
-
But that's true about AWS even!
End of conversation
New conversation -
-
-
that is exactly what they are - http request and response handlers - firebase cloud functions are literally express route handlers
-
Not really. Serverless is about building event driven applications. HTTP requests are only one kind of the events that can be handled
-
At some point you have to serialize the function call ...
-
Yes, the tweet was directed to
@soederpop. My point was that HTTP req are not necessarily the only source of events that could trigger a fn -
you’re right - at least w fb cloud functions I’ve also set up db triggers and such. I think the rails controller metaphor is still great
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.