Re:Why Netflix Rolled Its Own Node.js Functions-As-a-Service...
by jshen on Sunday October 28, 2018 @08:12PM
(#18324044)
Serverless includes other things like google app engine and Heroku.
[ Parent
| on HN ]
Re:Why Netflix Rolled Its Own Node.js Functions-As-a-Service...
by fouc on Sunday October 28, 2018 @08:41PM
(#18324144)
I haven't heard of those being called serverless. Those are more PaaS I guess.
Re:Why Netflix Rolled Its Own Node.js Functions-As-a-Service...
by jshen on Sunday October 28, 2018 @10:38PM
(#18324610)
It’s a spectrum and the boundaries are unclear. By this definition https://www.cloudflare.com/learning/serverless/glossary/serv... they are more serverless than PaaS imo.
Either way, serverless is a superset of FaaS.
Re:Why Netflix Rolled Its Own Node.js Functions-As-a-Service...
by jehlakj on Sunday October 28, 2018 @09:32PM
(#18324321)
He could have meant that it’s an ambiguous term that could apply to other platforms.
Re:Why Netflix Rolled Its Own Node.js Functions-As-a-Service...
by nwsm on Sunday October 28, 2018 @10:03PM
(#18324456)
Firebase seems more fitting for "serverless" than those
Re:Why Netflix Rolled Its Own Node.js Functions-As-a-Service...
by mandelbrotwurst on Sunday October 28, 2018 @08:28PM
(#18324090)
Does it? I always just considered those IaaS and thought "serverless" basically meant AWS Lambda or any comparable service (for which I agree FaaS is quite apt).
Re:Why Netflix Rolled Its Own Node.js Functions-As-a-Service...
by hawaiianbrah on Sunday October 28, 2018 @08:33PM
(#18324107)
GAE and Heroku are considered PaaS - Platforms as a Service
Re:Why Netflix Rolled Its Own Node.js Functions-As-a-Service...
by jshen on Sunday October 28, 2018 @10:39PM
(#18324616)
I think they are more serverless than PaaS by this definition. https://www.cloudflare.com/learning/serverless/glossary/serv...
Re:Why Netflix Rolled Its Own Node.js Functions-As-a-Service...
by manigandham on Sunday October 28, 2018 @11:18PM
(#18324814)
Cloudflare usually puts out good info but this is really bad marketing material stretched way too far to make a point, because they have their Workers platform and want to ride the "serverless" hype train.
Everything mentioned in that diagram is completely arbitrary and varies for every single vendor.
Re:Why Netflix Rolled Its Own Node.js Functions-As-a-Service...
by jshen on Monday October 29, 2018 @12:53AM
(#18325164)
What’s a good definition of serverless in your opinion?
Re:Why Netflix Rolled Its Own Node.js Functions-As-a-Service...
by manigandham on Monday October 29, 2018 @07:20PM
(#18332571)
Serverless doesn't have a good definition because it's not a real concept.
At most lambda/workers/functions are really just PaaS, except instead of uploading all of your code, it's just a single file with a single endpoint.
If we really need a new term, then micro-paas or FaaS works fine, although most FaaS vendors are expanding to running any arbitrary container with multiple endpoints, so we're right back to normal (but modern) PaaS at the end.
Re:Why Netflix Rolled Its Own Node.js Functions-As-a-Service...
by hawaiianbrah on Monday October 29, 2018 @02:38AM
(#18325469)
Okay, sure. But from their own websites:
Deploy and run apps on today's most innovative Platform as a Service [1]
Google App Engine is GCP's platform as a service (PaaS). [2]
[1] https://www.heroku.com/platform
[2] https://cloud.google.com/docs/overview/cloud-platform-servic...