Why Netflix Rolled Its Own Node.js Functions-As-a-Service Runtime

Re:Why Netflix Rolled Its Own Node.js Functions-As-a-Service... by daxfohl on Monday October 29, 2018 @12:32AM (#18325077)

Just remember the modern definition of serverless:

1. Not using a server.

2. Using a server. Not serverless.

Problem solved.

[ Parent | on HN ]

Re:Why Netflix Rolled Its Own Node.js Functions-As-a-Service... by aikah on Monday October 29, 2018 @12:37AM (#18325097)

> Just remember the modern definition of serverless:

Just because it runs on someone else's machine doesn't mean it is "serverless". an API Gateway obviously is a server.

FAAS is just a good old worker queue, there is nothing new about that.

There is no "modern definition" of serveless. it's just marketing, it has nothing to do with technology. Developers shouldn't use that word and expect to be taken seriously.

[ Parent | on HN ]

Re:Why Netflix Rolled Its Own Node.js Functions-As-a-Service... by olalonde on Monday October 29, 2018 @01:22AM (#18325248)

That's a good definition for P2P, not for "serverless". Serverless functions run on a server. It typically refers to a category of PaaS which allows on-demand code execution (as opposed to "always on" services).

[ Parent | on HN ]

Re:Why Netflix Rolled Its Own Node.js Functions-As-a-Service... by icebraining on Monday October 29, 2018 @03:57AM (#18325713)

I believe the idea is rejecting that definition.

[ Parent | on HN ]