News for hackers. Stuff that matters.
Re:Back to the '70s with Serverless by mattmanser on Saturday December 19, 2020 @08:15PM (#25482980)
Everyone's chasing "scalable", mostly for no reason at all.

There's also this enduring myth you see repeated even here of how much saving there is by not having "devops", when only very big companies needed them in the first place. A few minutes per month is the most devops any startup would need to do in reality running their own VMs or servers, after an hour or two of setup. And that hour or two is often less than faffing around getting all the labyrinth moving parts of AWS/Azure/etc. working.

And the whole thing becomes a transparent farce when you look at providers like Azure, where their own admin interface is so slow and prone to random breaks you have to ask:

How is this scalable?

It's clearly not scalable for themselves, so how is it "scalable" for everyone else?

There are benefits, mainly for me I'll use them for hassle free deploys[1], but the whole thing sometimes feels like a massive con to sell the performance of a potato by advertising it as a jet engine.

[1] Like a month back I deployed a demo prototype web app I wrote in 3 hours onto Azure straight from github with like two clicks, and got the contract, can't really beat that.

Re:Back to the '70s with Serverless by thethethethe on Saturday December 19, 2020 @10:01PM (#25483458)
> There's also this enduring myth you see repeated even here of how much saving there is by not having "devops", when only very big companies needed them in the first place.

I dunno, the first company I worked at was very small, under 30 people, sales included, and I was hired on as an SA. If they were using serverless, they would not have needed to hire me.

Deployments and system upgrades were very toilsome. The dev lead would spend a few hours deploying new code and we’d only do it around midnight in case there was a problem (our customers were almost entirely US based). I spent a lot of my time automating OS upgrades on the web servers behind our proxy. All of this work would be unnecessary for that small company if they were using serverless.

Additionally, as mentioned before, the majority of their traffic was during the day so they could have scaled down automatically at night, cutting costs. Would this be cheaper than running machines 24/7? I’m not sure, but I could see why you’d be interested in at least looking into it

Re:Back to the '70s with Serverless by kortilla on Saturday December 19, 2020 @11:52PM (#25483967)
> Deployments and system upgrades were very toilsome. The dev lead would spend a few hours deploying new code and we’d only do it around midnight in case there was a problem (our customers were almost entirely US based). I spent a lot of my time automating OS upgrades on the web servers behind our proxy. All of this work would be unnecessary for that small company if they were using serverless.

Not using serverless doesn’t mean there can’t be a CICD pipeline.

Re:Back to the '70s with Serverless by thethethethe on Sunday December 20, 2020 @02:12AM (#25484535)
Yeah of course. I’m not saying that serverless is the only ci-cd solution, many businesses build ci-cd pipelines on top of serverless apis. However, most serverless platforms take care of a lot of the deployment process out of the box, which would have been enough for the business I was describing in my comment
Re:Back to the '70s with Serverless by winrid on Sunday December 20, 2020 @01:02AM (#25484231)
You don't even need serverless for those things. Any of the automated deployment/orchestration systems in the last ten years solve those problem (ansible, terraform, etc).
Re:Back to the '70s with Serverless by thethethethe on Sunday December 20, 2020 @02:09AM (#25484524)
Yeah it’s true but it requires a lot more config. The job I mentioned in my comment involved thousands of lines of anisble to perform operations you wouldn’t even need to consider/could perform in a few clicks when using a serverless platform.

Don’t get me wrong—serverless platforms are not a ci-cd silver bullet. Many organizations build pipelines on top of serverless deployment apis, but it certainly does take care of a lot of things for you—not to mention other features mentioned elsewhere in my comments

Re:Back to the '70s with Serverless by 1337shadow on Sunday December 20, 2020 @06:13AM (#25485463)
You're supposed to encapsulate those in reusable roles, see an example methodology here: https://yourlabs.org/posts/2020-02-08-bigsudo-extreme-devops...

And since we have containers it's become really much easier actually ... Deploy a Traefik container which will watch dockerd socket and self-configure HTTPS and all when your other script starts container. Really, it's much easier than back in the days: https://github.com/jpic/bashworks/tree/master/vps

Re:Back to the '70s with Serverless by nojvek on Sunday December 20, 2020 @03:55PM (#25489424)
Wasn’t the original post complaining about avoiding a gazillion lines of config in the first place ?
Re:Back to the '70s with Serverless by 1337shadow on Sunday December 20, 2020 @08:00PM (#25491087)
Lines of config are like lines of code, refactoring them regularity is basic hygiene like brushing your teeth. You can "have no config lines" if you go ahead and click your config but then you don't have "infra as code" anymore so that's also "going back to the 70's" I guess.
Re:Back to the '70s with Serverless by 1337shadow on Sunday December 20, 2020 @05:54AM (#25485371)
When your infra is in AWS, you need an "AWS Certified DevOps"[0] instead of a "typical DevOps", I mean, the typical OSS hacker - which is kind of sad really, and makes me wonder: is this how we're going to build an Idiocracy[1] ? Anyway, things like backups, monitoring, alerting, debugging, is going to be a requirement anyway, and for me it's harder when locked in proprietary stuff such as AWS, I'd rather have OSS I have freedom to hack ;)

[0] https://aws.amazon.com/certification/certified-devops-engine... [1] https://en.wikipedia.org/wiki/Idiocracy#Plot

Re:Back to the '70s with Serverless by grey-area on Sunday December 20, 2020 @03:45AM (#25484884)
I don’t think your past experience reflects current practice.

My reality at a 20 person shop with a few devs is much closer to the OP - a few hours setup (we save the cloud config and can remake servers in a few minutes), servers run for months without intervention, uptime is on par with cloud services, deploys take seconds. Managing servers or deploys just are not major problems for us.

Serverless is not a solution to deploy problems - mostly because they’re just not significant problems for us, if anything the dev deploy story is worse than renting VMs. It’s an interesting take on serving requests and I do believe some variant of it might be the future (a variant more like cloudflare workers IMO), but at present there are serious drawbacks and it is not clearly better, particularly when provided by a predatory company like Amazon.

Re:Back to the '70s with Serverless by manigandham on Sunday December 20, 2020 @03:01AM (#25484714)
All you needed was PaaS, which has existed for a long time. Or the even older name: managed services, offered by pretty much any decent hosting provider for decades.

I remember using companies like MediaTemplate and FullControl 10 years ago for clients and not having to worry about OS updates.

Re:Back to the '70s with Serverless by thethethethe on Sunday December 20, 2020 @03:13AM (#25484758)
Serverless is a PaaS. And yeah, those services could work too. Serverless isn’t the only solution that works.
Re:Back to the '70s with Serverless by empthought on Saturday December 19, 2020 @09:02PM (#25483184)
> A few minutes per month is the most devops any startup would need to do in reality running their own VMs or servers, after an hour or two of setup.

Right up until something crashes or some hardware fails.

Re:Back to the '70s with Serverless by jiggawatts on Saturday December 19, 2020 @09:29PM (#25483322)
> Right up until something crashes or some hardware fails.

Unlike the public cloud where Nothing Ever Goes Wrong (tm).

There are never brownouts.

There are never latency spikes.

No undocumented quota limits.

Documented but confusing quota limits.

Unexpected performance issues caused by other customers.

Forced upgrades.

Forced patching.

Shock bills.

No siree Bob, that kind of thing just doesn't go on in the public cloud! It's all rainbows and unicorns....

Re:Back to the '70s with Serverless by empthought on Saturday December 19, 2020 @09:59PM (#25483449)
I fail to see how this supports your claim that you can get by with "a few minutes per month" of devops. In fact, it's a classic red herring.

Your original claim is quite unrealistic and you'd do well to retract it. It's bad advice both for public cloud and for self-managed efforts alike.

Re:Back to the '70s with Serverless by daniellarusso on Sunday December 20, 2020 @01:02AM (#25484230)
When I used to work for an MSP, we would sell Dell servers to rural banking groups.

We supported disaster recovery and high availability deployments.

Any failed component, Dell would send us a replacement in less than 24 hours.

Re:Back to the '70s with Serverless by AnIdiotOnTheNet on Sunday December 20, 2020 @09:19AM (#25486337)
24? I guess it's that long because it is rural? We use Dell servers and I sleep a bit better having seen their 4hr support replace a motherboard with a bad lifecycle controller within 2 hours of the initial call.

Try calling Amazon and getting that kind of response for your problems.

Re:Back to the '70s with Serverless by daniellarusso on Sunday December 20, 2020 @11:14AM (#25487225)
Yeah, my closest Target store and major airport is over 2 hours away.

But, yeah, that is worse-case scenario.

Re:Back to the '70s with Serverless by kortilla on Sunday December 20, 2020 @03:05AM (#25484729)
But it is a few minutes per month. A properly architected application won’t depend on a single server so a hardware failure will be as unimportant as it is the serverless world.
Re:Back to the '70s with Serverless by empthought on Sunday December 20, 2020 @07:26AM (#25485797)
Architecting a system properly is one of the key functions of devops. You don’t get it by investing a few minutes per month, whether public cloud or bare metal.
Re:Back to the '70s with Serverless by rpedela on Saturday December 19, 2020 @09:56PM (#25483444)
You have all that DIY too, except maybe shock bills, but it's your problem to fix. Like with everything, extremes are bad and all managed or all unmanaged are both bad. My personal guideline is use off-the-shelf services if they are cheaper than DIY, including labor, or if DIY provides no competitive advantage and off-the-shelf is cheap enough. But if DIY is much cheaper or gives a competitive advantage, do it yourself.
Re:Back to the '70s with Serverless by tluyben2 on Sunday December 20, 2020 @01:14AM (#25484287)
You do not notice that either with the right setup. I also rather hire a good SA and pay 10-100x less monthly (for which I can hire an army of devops here in the eu by the way) with the risk of all hardware dying at the same time (which does not happen, not now, not in the 90s when I started hosting).

Sure serverless etc has it's upsides and in that case I do use it, I just encounter close to 0 companies per year that need it or benefit from it. Aws ways benefits.

Re:Back to the '70s with Serverless by grey-area on Sunday December 20, 2020 @04:08AM (#25484950)
The choice is not only serverless or hosting on bare metal - there are a lot of options in between. You can hire VMs and have the vendor transparently deal with hardware faults for example without downtime. Running your own VMs doesn’t mean running your own hardware.

The original claim is not at all unrealistic, I’ve been running a small shop with about 20 VMs without issues for years, uptime seems to me about comparable with serverless or hosted services from big players who regularly have small outages and there really is very little work involved.

Re:Back to the '70s with Serverless by FpUser on Saturday December 19, 2020 @10:12PM (#25483515)
I always have standby copy deployed elsewhere. And I make it a point not deploying production until a single script could rebuild new clean system by using backed up data, configs and software packages. So for me it is no a big deal at all. Well if the hardware died I have to pay for replacement which is not fun but it is a very rare occurrence.
Re:Back to the '70s with Serverless by otabdeveloper4 on Sunday December 20, 2020 @01:38AM (#25484404)
Yes, "the cloud" is bunk from any technical point of view.

It exists to shift CapEx to OpEx for accounting. Any technical considerations are a distant third place on the list.

Re:Back to the '70s with Serverless by 3pt14159 on Sunday December 20, 2020 @03:29AM (#25484814)
Well, if you mean CapEx because one needs fewer programmers and a higher AWS bill, then yes I agree with you. But if you mean CapEx because one needs fewer physical computers that they own and a higher AWS bill for computers that they rent, then no I do not agree with you.

First, the markup in just sheer ops terms is enormous. Minimum 4x, and in some cases 20x. Sure, you get a couple more nines of reliability, but 99% of startups don't need that much reliability.

Second, in countries like Canada where capital expenditure on computer systems can be heavily marked down[0] people still use AWS and DigitalOcean by default.

The main reason people don't do colocating is that it is a waste of time better spent. DigitalOcean is cheap enough. AWS is cheap enough and if the team doesn't have experience running Postgres, fine, they use RDS. Sometimes it's just sheer laziness at first that later blossomed into "holy shit, we're growing too fast to even think about migrating off of these giant AWS bills" which was essentially Dropbox's story if I recall correctly.

[0] 55% per year, and in practice they allow full expensing in the first year for petty amounts of outlay. For example, if your business is a data centre, sure it's 55% per year, but if you run a flower farm and fully expense a new laptop for sales the CRA is generally fine with it.

Re:Back to the '70s with Serverless by otabdeveloper4 on Sunday December 20, 2020 @09:07AM (#25486269)
I'd guess that the vast majority of "cloud" customers are boring enterprises doing boring enterprise stuff, probably not even Internet-related stuff at all.
Re:Back to the '70s with Serverless by flyinglizard on Sunday December 20, 2020 @02:11AM (#25484530)
That can happen without serverless - renting VMs is OpEx enough.
Re:Back to the '70s with Serverless by otabdeveloper4 on Sunday December 20, 2020 @02:40AM (#25484641)
Yes, if you manage to shift the responsibility of maintaining these VMs on the developer positions you already have.
Re:Back to the '70s with Serverless by noizejoy on Sunday December 20, 2020 @02:39AM (#25484636)
Leasing programs did that well before the cloud ever came along
Re:Back to the '70s with Serverless by otabdeveloper4 on Sunday December 20, 2020 @09:04AM (#25486256)
"The cloud" is a leasing program except even more optimized for OpEx - pay-as-you-go monthly billing and you now don't even need to hire ops people because it's "serverless".

(Of course you have to force your devs to do the ops stuff now, but that's not accounting and HR's problem now.)

Re:Back to the '70s with Serverless by WJW on Sunday December 20, 2020 @12:19PM (#25487800)
> Everyone's chasing "scalable", mostly for no reason at all.

No technical reason, maybe. There is a social reason though: if you point out that there is no need to build scale (yet), you are pointing out that the business will not achieve overnight success. Even if it's true, it kills excitement and is therefore not something that people want to hear. Who wants to realize that what they're spending large amounts of time on (and possibly even neglecting other things like health, sleep and social contacts) will not even make all their financial dreams come true? Much easier to not think too hard about it and keep on doing what everyone is doing.

So, building out scalable infra is signaling that you too believe in the company and are preparing for the moment (any time now!) that "webscale" is needed. It's showing that you are part of the team.

Re:Back to the '70s with Serverless by throwaway2048 on Saturday December 19, 2020 @09:04PM (#25483199)
Its like a well stocked grocery store with thousands of brands, I think the biggest draw of "the cloud" is the illusion of infinity plenty, all you need to do is press a button (even though the reality really doesn't measure up, at least not in ways people naively assume)
Re:Back to the '70s with Serverless by BaronSamedi on Sunday December 20, 2020 @07:15AM (#25485747)
Scalability is just one reason for using serverless. There are many others. Most of which have to do with being able to focus on the part of your code that actually does something instead of on infrastructure and integration. For example, not having to configure and maintain VMs, containers, or Kubernetes, off-loading a part of security onto the cloud provider, and built-in integration with supporting services like logging and metrics.

Serverless, like every design decision, comes with its own set of trade-offs. Whether those trade-offs make sense for your environment is something you have to determine. At my company we have seen a productivity increase and shorter development times using serverless. Of course, that was after the learning curve which is certainly not trivial.

Re:Back to the '70s with Serverless by xnx on Sunday December 20, 2020 @08:20AM (#25486039)
I sometimes think of how far we still are from utility-quality computing services. Every company needs electricity with near-perfect uptime, but almost no company has a full-time electrician in-house.
Re:Back to the '70s with Serverless by sveme on Sunday December 20, 2020 @03:11AM (#25484754)
Does anyone know of a resource showing me some parameters for estimating how far different managed servers reach? How many concurrent users, bandwidth, etc.? Have a hard time getting a mapping for expected concurrent users -> hardware requirements. How quickly can you adjust the HW resources in a non-cloud setup if your startup product is more successful than expected?
Re:Back to the '70s with Serverless by skolsuper on Sunday December 20, 2020 @05:11AM (#25485179)
Impossible question, it depends what your app does and what your users do. Even within the same company, 1000 concurrent users of Google Maps will use completely different resources than 1000 concurrent users of gmail. It'll even change over time for the same app and same users, as their behaviour or the world around them changes.
Re:Back to the '70s with Serverless by tsss on Sunday December 20, 2020 @08:08AM (#25485974)
> by not having "devops"

Apparently, you don't even know what that word means. You can not "have" DevOps. It's a methodology and not a thing. Besides, DevOps means exactly the opposite of what you are implying: it is the practice of not having a dedicated operations team and letting devs handle as much of the operations for their own applications as they can.

> few minutes per month

I can tell you my team spends a good 30% of its time on operations. Some of that (for example adminstrating K8S clusters) could be offloaded to cloud providers for money.

Re:Back to the '70s with Serverless by waheoo on Saturday December 19, 2020 @08:30PM (#25483040)
Makes me think of those old "Webscale" skits on YouTube.
Re:Back to the '70s with Serverless by amiga-workbench on Saturday December 19, 2020 @09:36PM (#25483352)