So yeah, after that conversation I genuinely think that "Framework as a Service" describes what's interesting about the shift.
-
-
But generally the push and pull is that with enough demand comes new OSS solutions. Rails was harder to ops than PHP, still highly adopted.
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Lambda support exists at language level, not framework level. You're not really locked into framework features unless that changed?
-
You are because you can't (or shouldn't) run stuff like a router inside your function. So you're reliant on Lambda to perform the role ...
-
traditionally filled by in-process frameworks.
End of conversation
New conversation -
-
-
FWIW we think about this a lot at Firebase wrt Cloud Functions. We want it to feel like a friendly primitive you can extend.
-
Paradoxically we currently accomplish this by being *more* opinionated and building programmable superstructures on the raw compute product.
-
Yeah that sounds about right (and not paradoxical).
End of conversation
New conversation -
-
-
Feels like if you write code that responds to events you can be relatively vendor independent. How diff can amz and azure http event be.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
No reason things like RDS / Lambda / S3 can't be offered on K8s, eliminating cloud vendor lockin. Lots of in progress already on this in OSS
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This is where Kubernetes comes in. Serverless / FaaS on Kube is > Lambda. Kubernetes needs to become standard deployment model.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.