How would you describe that which is called "serverless"?
Do you mean that the routing is outside the deployed app and in the "framework" (lambda, etc)?
-
-
yes! exactly. we don't have a web framework here; it's present in the uhhh serverless framework/platform/whatever you wanna call it
-
So you have a framework but it's hardcoded in the platform, right?
-
mostly. it doesn't have to be hardcoded tho. which is why i like thinking of it as an event-driven distributed container-spinning-up infra
-
Will it eventually just devolve to a graphQL interaction? It seems like the only way to avoid some eventual “server-less” vendor lock-in.
-
GraphQL is not magically non-proprietary ;)
-
I don’t know enough to debate graphQL encumbrances. I meant the benefit of JS asking 4 what it’s needs, unconstrained by RESTful endpoints.
-
Why are RESTful endpoints more constraining than GraphQL?
-
Every RESTful API I’ve worked with has required both client and server changes to provide additional data in one round trip. Not w/GraphQL
- 1 more reply
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.