91–100 of 266 posts
Earlier quoted context omitted.
I still fail to understand why 4 years in, people seem to be confused about the idea that definitions of words involve over the years and that the computer industry has both been coining and adopting phrases. But a quick Google search is all that it would take to “understand it” https://en.wikipedia.org/wiki/Serverless_computing
I can't wait until society swaps the meaning of left and right through memes
What about email signing?
After surrendering all your data to a cloud provider?
Earlier quoted context omitted.
When you are just using a VM - it’s your responsibility to keep the VMs and the runtimes patched, design a scaling solution, etc.
Managed hosting is used in at least two different ways: * As a synonym for dedicated hosting. E.g. you rent a machine, and run what you want on it. And have to patch stuff etc. * As a separate tier of service above dedicated hosting where the hosting provider is responsible for running the services on the machine. Some managed hosting providers will take responsibility for scaling too, though often it will be a semi-…
Earlier quoted context omitted.
The benefits to using this approach over a traditional server are: 1. Someone else maintains the software running these services, including OS upgrades, security upgrades and patches, uptime monitoring, etc. 2. Since every logical component is an independent service, each scaling independently, any one single component is unlikely to become a bottle-neck while scaling. In traditional monolithic servers, you'll have t…
> 1. Someone else maintains the software running these services, including OS upgrades, security upgrades and patches, uptime monitoring, etc. This is the standard marketing phrase echoed to promote serverless. By experience, I don't think is valid. Packages like unattended-upgrades automates all this stuff. Also, not being able to verify what the software is doing is scary and looks like a 10 steps backwards to me.…
Serverless to me is abstracting all the cloud providers away for provisioning, and it's first class. If Lambda's down, whatever hardware you could build and ship to a data center is down too. I now have access to the same critical data center tools.
Also code completion. Take my code, and rewrite for performance and security. Run it on some OS that is always rewriting itself. I want the power not the grid.
Earlier quoted context omitted.
Do you also complain when people say they have a “bug” in their code or that they have a “server farm”? Are they literally watering the server floor and waiting for computers to grow?
Not at all. It's in this case, using the term serverless is akin to calling cloud based software (Google Docs, TurboTax, etc) softwareless. It's closer to calling a stop sign a "go sign" than descriptors from your example. Calling managed servers "serverless" is distinctively misleading.
Wouldn’t you be the first to criticize someone who didn’t take the time to understand other computer concepts that had been around for years and then attempted to speak intelligently about them?
Earlier quoted context omitted.
Do you also complain when people say they have a “bug” in their code or that they have a “server farm”? Are they literally watering the server floor and waiting for computers to grow?
There is a huge difference between a metaphor (resemblance) and contradiction (stating it is and isn't something at the same time).
I don't know anything about serverless --- to this day I fail to understand what this word is even supposed to mean. And the deployment diagram[1] sure looks complicated to me. I think I prefer old-school servers. [1]: " rel="nofollow">https://raw.githubusercontent.com/0x4447/0x4447-product-s3-e...
I still fail to understand why 4 years in, people seem to be confused about the idea that definitions of words involve over the years and that the computer industry has both been coining and adopting phrases. But a quick Google search is all that it would take to “understand it” https://en.wikipedia.org/wiki/Serverless_computing
Earlier quoted context omitted.
The less pessimistic interpretation is that it's like having someone else be your devops department. Unlike what people like to think, most people running traditional VMs and containers end up doing just as much devops as on a dedicated server (while doing consulting, I'd typically get more hours at higher rates out of people insisting on AWS, because getting an AWS setup right is a lot of work), so serveless is appe…
It's more than SSH access that you give up though. You have to bend to the paradigm completely or you're really fighting against it. For one example, I keep running up against wanting to delay an execution of one lambda from another. There are some truly horrible hacks out there to try and achieve that.
The irony is that a whole lot of the solutions are well understood; just not in the same environments. E.g. "enterprise" computing went through a whole cycle of building application services for small self-contained components with discovery and messaging in the late 90's that people seem to have largely forgotten as somewhere to look to at least for a laundry list of what kind of services are needed.
Earlier quoted context omitted.
I still fail to understand why 4 years in, people seem to be confused about the idea that definitions of words involve over the years and that the computer industry has both been coining and adopting phrases. But a quick Google search is all that it would take to “understand it” https://en.wikipedia.org/wiki/Serverless_computing
Not a single post on Hacker News can use the term "serverless" without the exact same replies being posted every time. It's as if a certain portion of the HN crowd simply cannot fathom that a new term exists and is in use, and instead resort to the same, tired responses.
Earlier quoted context omitted.
"serverless" is just "managed hosting" under a new name, I believe.
No it’s not just managed hosting. Managed hosting still means there is a server to maintain, patch, and that it is always running.