Re:Why Netflix Rolled Its Own Node.js Functions-As-a-Service...
by Waterluvian on Monday October 29, 2018 @09:35AM
(#18327375)
Yes! I've been advocating among my colleagues to perceive "serverless" as "functional programming -> web services"
I get that the allure of not focusing on infrastructure, scaling, etc. is strong. But that's really a side effect of what you're actually doing: applying FP principles to web service design.
And it really fits the paradigm well. You've got HTTP services (short lived, therefore comfortably stateless) that are ideally infinitely scaleable (easy to do when your HTTP services are basically pure functions). Do you need caching? That's like memoization of your functions!
I get that the allure of not focusing on infrastructure, scaling, etc. is strong. But that's really a side effect of what you're actually doing: applying FP principles to web service design.
And it really fits the paradigm well. You've got HTTP services (short lived, therefore comfortably stateless) that are ideally infinitely scaleable (easy to do when your HTTP services are basically pure functions). Do you need caching? That's like memoization of your functions!