So I'm no fan of whiny prescriptivism language complainers, but "serverless" really takes the cake for a pointlessly confusing neologism.
So the non-REST is a critical difference? Seems a little weird I think.
-
-
i don't think it's just non-REST — but if you're building a RESTful API in serverless, you're still architecting events
-
endpoints + requests give way to functions + events. it's a similar pattern, but it's general to serverless
-
But since you're not calling functions by reference you're still invoking something by endpoint name and params no?
-
yeah — like, we still have to handle requests. but a function's a whole container. there's no request-piping stack inside a function (nrmly)
-
so fundamentally, yes. you're still building a restful api where a request hits an endpoint. but that becomes an event…
-
What's a request piping stack?
-
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
- 8 more replies
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.