5 ms·
> serverless server? This isn’t a contradiction. “Server” is an overloaded term and the “server” in “serverless” refers to a different meaning of “server” than
by throwaway894345 6y ago
> serverless server?
This isn’t a contradiction. “Server” is an overloaded term and the “server” in “serverless” refers to a different meaning of “server” than the “email server” bit. “Serverless” means there is no physical or virtual hosts to manage, you just supply the request handler i.e., the email server. It's amusing because it sounds like a contradiction, but it's not one.
- darkwater 6y ago> This isn’t a contradiction. Yes it is. The "server" in "serverless" means no need to low-level manage/provision a server (computer) and its lifecycle. While "server" in "A serverless email server" means actually "service" as in "A serverless email service on AWS using S3 and SES". Which makes much more sense. The linked repo lets you have an "email server" just like GSuite gives you a "serverless email server".
- throwaway894345 6y agoI don't understand. You insist it's a contradiction but then go on to reiterate my own argument which demonstrates that it is not, in fact, a contradiction but rather using the same term ("server") to refer to two distinct concepts ("computer" vs "service")?
- darkwater 6y agoIt's a contradiction because it's an incorrect overload of the word "server".
- throwaway894345 6y agoWell, Oxford English Dictionary disagrees with you.
- cortesoft 6y agoSo if you get an omelette at a restaurant, I can call it an eggless omelette because I didn’t have to cook the eggs myself?
- throwaway894345 6y agoThis would make a lot of sense if the de-facto restaurant experience involved you cooking your own eggs, especially if the egg-cooking experience was notoriously laborious and expensive. If we swap "egg" and "cooking" with "VM" (or "bare metal" if it suits you better) and "maintaining", suddenly "serverless" doesn't sound so ridiculous.
- fxleach 6y agoNo no, it still sounds ridiculous.
- unethical_ban 6y agoIf "egg" was an overloaded term that meant the noun "egg" and the noun "process of cooking an egg for an omelette", then yes, you could.
- mypalmike 6y agoAgile isn't really agile. Cloud computing isn't really in clouds. Personal computers aren't that personal. Serverless isn't really serverless. Who cares.
- stonesweep 6y agoI disagree with your assessment, email is a service and not a server. A service can run on a server, or ephemerally as in this article (which still has servers underneath it, you're just not running them). S3 and SES are services running on servers.
- imwillofficial 6y agoYou are incorrect, see man pages.
- stonesweep 6y agoThis makes no sense (too abstract of a statement), but here let's try this: $ man systemd | head -4 | tail -1 systemd, init - systemd system and service manager An email daemon (Postfix, Exim, Dovecot, UW-IMAP, Sendmail, etc.) are services running on a server. An "email server" would be a server running a daemon to provide email service in this example.
- ape4 6y agoThis makes me think there should be a Linux tool to extract the Nth line of a file. With options to get the N-Mth lines, etc
- stonesweep 6y agoMan pages can be tricky as the content can vary distro by distro (how up to date is your copy of man-pages, what changes have happened, etc.) - this technique is pretty portable to extract the synopsis of a man page specifically due to the format it uses (most times I'd use like grep -A3 -B2 foo /some/file, e.g.).
- ape4 6y agoUgly way to get the first indented line: `man systemd | grep '^ ' | head -1` Which is the summary
- mgkimsal 6y ago"means there is no physical or virtual hosts to manage" We're just swapping one type of management for another, really. Becoming proficient in all the permutations of AWS stack, for example, to * make sure you don't get overbilled, * have appropriate memory/limit resources on your lambdas, * have correct backup/redundancy on s3, * make sure all your IAM policies are correct and not allowing malicious actors, etc. and more... it's ... just a different set of things to worry about. Yay - I don't have a 'server' that can go down. I now just have to make sure I don't get billed $87k because I forgot to click the correct button.
- kixiQu 6y agoBilling exists for servers as well. Servers need to be configured as do lambdas. Servers also have backup needs. Servers also present security problems of access. It's not that hard to configure a lambda to run in just as limited a way as a physical machine. Not having to worry about MCEs or disk failure patching makes the concerns less like a "different set" and more like a subset of things to worry about relative to managing servers. I know most of this stuff is really well trod-over, but from your comment I think one'd get the impression that people are switching just because of a trend or something, not because there's an actual layer of management they're paying to have outsourced. (I would acknowledge that view of it being a subset rather than a different set is invalid once you're debugging performance at a gritty level, where cold starts etc. etc. introduce their own equivalent layer of complication, but most people doing most things never need to)
- twistedpair 6y agoAmen. How many times did you update your Node.js AWS Lambdas or GCP Cloud Functions because of the Linux kernel CVE of the week? You didn't because all you're responsible for is your few lines of Node.js logic that kept on scaling and humming along. The cloud vendor cares for the rest.
- vinay_ys 6y agoJust because you didn't doesn't mean they did and you didn't actually have any vulnerabilities. There is no such provable attestation of security in serverless model.
- xdennis 6y ago> “Serverless” means there is no physical or virtual hosts to manage While true, that's not the defining characteristic of "Serverless" because PaaS also does not require server management.
- megous 6y agoIt's indistinguishable from a regular web hosting. You just upload script to some ftp and don't manage anything either. You just configure links to other services like DNS, or DB if that's needed. It's just now the same thing is done via some proprietary/custom cli tools and/or APIs not via a standard protocol and a trusty old clients that are already in your distro, and it's branded differently. APIs are good for some uses. That's usually lacking with hosting providers. Other than auto-scaling I can also easily bankrupt myself with if I make a mistake, I don't see much qualitative difference. Only in the details.
- twistedpair 6y agoCloud 2.0 "serverless" often expects: - Just add code/logic - Scales to zero (zero calls to your endpoints, $0/mo) - Scales up automagically to match load - You don't do anything to provision/patch servers (e.g. FaaS) Classic PHP shared hosts don't meet this definition because: - You paid a flat monthly hosting fee (e.g. Dreamhost) - You only scaled to 1 node (need more, too bad) True, you didn't usually need to mess with PHP.ini or Apache server installs and configs, but you still didn't get the same benefits as modern serverless.
- antihero 6y agoI wonder if you could, for reasons, make a set-up where you upload your PHP files to an S3 bucket, and then have a API Gateway or Lambda which basically just serves the files from the bucket, and if they are PHP, executes them with a Lambda PHP runtime. So you hit /index.php -> checks S3 bucket for index.php -> executes that with lambda and gets string of response -> returns it to original lambda -> serves up to client.
- throwaway894345 6y agoI'm a little confused about why you're responding to me. I think I agree with everything you're saying, but I'm not sure where the comparison with PHP hosting is coming from. Are you sure you responded to the right thread?