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 scarface74 on Monday October 29, 2018 @11:36PM (#18333861)

Data Lakes, Data Factories, and event hubs just sound like gobbledygook to me and if they are “exactly the same as thier underlying concepts”, those concepts mean no more to me than the term “serverless” mean to the uninitiated and I’ve been developing professionally for over 20 years. It’s the developers responsibility to pick up on industry jargon just like I had to do a year ago as the Dev lead when the company I worked for wanted to “move to the cloud”. I thought AWS was just a bunch of VMs a year ago.

I had heard of “Nosql” two years ago but I didn’t know what it was until I was hired to implement two projects on top of Mongo. Did I complain about the use of the term “NoSql” every time someone mention it? No, I learned Mongo inside out so I wouldn’t design something non scalable and non redundant.

[ Parent | on HN ]

Re:Why Netflix Rolled Its Own Node.js Functions-As-a-Service... by manigandham on Tuesday October 30, 2018 @02:34PM (#18339939)

You keep answering about yourself, I'm talking about the entire industry. For every one of you, there were 100 people who used MongoDB because its "fast, cool, noSQL".

It's great that you research, but many do not. Hype, jargon, and excessively misleading terms are real, and they make a measurable impact on productivity and confusion. This is why marketing and branding is so important when naming, and its why there should be an effort made to use better terms.

I still haven't heard a single argument on why we shouldn't do better, other than that you can handle it. Good for you, but that's not the point.

[ Parent | on HN ]