News for hackers. Stuff that matters.
Re:What We Lost with PHP and jQuery by p_ing on Sunday June 01, 2025 @12:14PM (#44151914)
Running your own infrastructure is expensive.
Re:What We Lost with PHP and jQuery by Hobadee on Sunday June 01, 2025 @12:17PM (#44151930)
Have you seen a cloud bill recently!? My buddy worked for a company that was spending a million on their monthly AWS bill. You can easily buy all your own infra, plus hire an engineer or two for the price that some of these companies are dropping on "inexpensive" cloud services.
Re:What We Lost with PHP and jQuery by paulryanrogers on Sunday June 01, 2025 @12:25PM (#44151994)
Now add SOC and PCI compliance, DR with RTO, HA, etc. No doubt it could still be cheaper. But self managed infra does add up quickly.
Re:What We Lost with PHP and jQuery by dijit on Sunday June 01, 2025 @12:33PM (#44152061)
You don’t get away from any of those by hosting in a cloud.

Your colo provider should be doing their part for physical access for ISO27001/SOC2 and PCI-DSS.

I quite literally know all about this because I was running payment card infrastructure in a colo, as part of one of the largest e-commerce software suites in the UK at the time.

Re:What We Lost with PHP and jQuery by paulryanrogers on Sunday June 01, 2025 @02:51PM (#44152951)
Indeed. But cloud can provide a faster and easier path to getting there, at least IME.
Re:What We Lost with PHP and jQuery by dijit on Sunday June 01, 2025 @02:56PM (#44152988)
No?

Cloud gives you direct access to compute at the click of a button (provided you have quota).

The ISO/PCI cert requirements are not accelerated by their use, only the initial deployment speed of your solution. If at all anything the latest I've seen is that there are more checks in cloud for various areas where you can accidentally leak data through poor permissions or because someone could enable those permissions.

For example in Google Cloud there was an additional requisite that I monitor any admin users oauth2 application accesses for their google accounts; this was not a requirement for on-prem.

Re:What We Lost with PHP and jQuery by paulryanrogers on Sunday June 01, 2025 @06:13PM (#44154127)
Yes?

At least in my experience as a service provider.

With cloud I can easily plug in a compliance vendor like Drata, add connectors to my other vendors, and get a significant amount of evidence quickly.

Bespoke on-prem solutions bring plenty of their own challenges that are just N/A or handled by cloud vendors, like physical security.

Maybe as a payment processor things shake out differently. Though having read far more of PCI v4 than I'd like, I doubt it.

Re:What We Lost with PHP and jQuery by jauntywundrkind on Sunday June 01, 2025 @01:26PM (#44152431)
And any one of those could become an existential risk, could take down your entire company.

Do you trust your people to never slip up? To make sure there's really the reliability & security guarantees that your company depend on? Are there competent technical hands available at all times to handle issues as they come up? This adds significantly to the org chart, requires constant caring to be added, to keep it steered and staffed.

I'm a huge fan of self hosting, of buying your own hardware. Especially for very technical entities, that have lots of overlap & intimacy with computers. But your company needs to have reason to believe it can do the job not just well, but to a degree where you're sure you won't lose the entire business. Needs to believe they really are on top of this huge domain! I see very clearly why folks go cloud, and I wish the world was in a better position, had more to say, to show why buying pizza boxes is gonna not just save you money buy be an enduring acceptable safe choice.

Much safer to not wade in here, shutting the hell up is free, and there's plenty that can go wrong, but I do think Kubernetes presents the first maybe acceptable opportunity for broadly acceptable DIY computing, delivering key three things: an essential integrativeness of concerns allowing it to be a comprehensive cross-cutting platform for your business's compute, delivers strongly on the security and dependability you absolutely must have in a well known way, and avoids the historical trap of each company ending up married to their own specific boondoggle infrastructure that's been hand cobbled together by whomever had such and such task at the time. There's a stable practice here, one that many companies and practitioners are honing; there's much difference between Kube clusters sure, but these intracacies and elaborations support the creation of something that is mostly alike, if you look from one company's clusters to the next.

Re:What We Lost with PHP and jQuery by luckylion on Sunday June 01, 2025 @02:45PM (#44152910)
Would you trust cloud providers to never slip up though? I don't think the split is "perfect but pricey" vs "less expensive but shaky". It feels similar to the autonomous driving question, where safety of autonomous driving is often compared to perfection instead of human drivers.

Would UniSuper engineers have trashed their entire infrastructure the way Google Cloud did? Granted, that's not a common thing to happen, but they got _very_ lucky that day that they had a backup elsewhere and didn't fully commit to trusting Google.

Re:What We Lost with PHP and jQuery by paulryanrogers on Sunday June 01, 2025 @02:53PM (#44152971)
There is an element of "never fired for buying IBM" involved. If AWS screws up then theoretically they've a bigger bank roll for any settlement or judgement.
Re:What We Lost with PHP and jQuery by jauntywundrkind on Sunday June 01, 2025 @10:04PM (#44155279)
Nothing's perfect? But theres a lot of orders of magnitude difference in investment in what most companies can and will do versus what a hyperscaler will!

And while your company is a single petri dish with your own specific problems, these folks have to see a lot of shit. Sometimes yes it all goes bad even there anyways! The resiliency fails! But given how much they've thought about it & how much they've hedged against 1 in a million 1 in a billion cases that they see semi regularly that your company might never notice until it's too late, I think there's a ton of reasons to trust these generally very well exercises systems with pretty sizable engineering teams & deployments behind them. More so than what most folks can bring to bear.

These matters are existential threats for your business. And they are existential threats for big providers, for HyperScalers, even more so. Google very publicly owned up to UniSuper, found out why it happened (a blank form on an internal tool lead to the account having a 1 year time limit with auto-deletion), and publicly announced their three fold plan to make sure at least this specific horribly threat would never happen again:

> We deprecated the internal tool that triggered this sequence of events… We scrubbed the system database and manually reviewed all GCVE Private Clouds… We corrected the system behavior that sets GCVE Private Clouds for deletion for such deployment workflows.

https://cloud.google.com/blog/products/infrastructure/detail...

The mere fact that this was such a notable event should be itself notable. In general, the hyperscalers have been stupendously reliable. And absurdly secure. They have small armies dedicated insuring both.

I look forward to this new era where finally we might have computing of our own good enough & broadly known & trusted enough to make doing our own - even with small teams - viable!! But heavens yes, keep off-site backups!!!

Re:What We Lost with PHP and jQuery by luckylion on Monday June 02, 2025 @05:23PM (#44163181)
The scale becomes not quite as impressive if you consider that those thousands or tens of thousands of engineers also maintain hundreds more services in vastly more complex scenarios because they need to cover many more use cases than yours. Most companies don't need to run everything AWS has to offer, so they wouldn't need to handle all of that complexity.

Individual AZs have significantly worse uptime than any DC I've ever worked with. They are very reliable, if you are multi-region - and you hire a small army of consultants.

Re:What We Lost with PHP and jQuery by sixtyj on Sunday June 01, 2025 @02:41PM (#44152883)
You can read DHH tweets how move from cloud to own infra was -90% of monthly money.
Re:What We Lost with PHP and jQuery by dijit on Sunday June 01, 2025 @12:17PM (#44151928)
yet, it costs 1/5th of what cloud does with any kind of minor load.

Someone needs to study these claims tbh; your point is contrary to my experience.

Re:What We Lost with PHP and jQuery by r3trohack3r on Sunday June 01, 2025 @12:24PM (#44151987)
I think when some people say “self hosting is expensive” they factor in the cost of the engineering talent necessary to successfully sysadmin the setup and ongoing maintenance - and the cost/risk of shopping for and evaluating that skillset to find and retain an engineer that isn’t going to muck the whole thing up.

You can subsidize the cost of self hosting by discounting your time/skill in DIY - and you don’t have to interview yourself.

Re:What We Lost with PHP and jQuery by mrweasel on Sunday June 01, 2025 @12:32PM (#44152052)
> they factor in the cost of the engineering talent necessary

You need to do that for cloud as well. The assumption that you can just get the developers to spin up what they need doesn't work. You need a team of "cloud engineers" if you don't want your cloud bill to go crazy. I know a few people that does AWS for clients, they basically spend all their time maintaining, upgrading and reworking things to reduce the cost.

In one example, when AWS changed their IPv4 pricing, one of the went in an managed to remove 90% of their public IPv4 usage. You need to say on top of the cloud platforms, ensuring that costs stay low is a full time job.

Re:What We Lost with PHP and jQuery by dijit on Sunday June 01, 2025 @12:26PM (#44151999)
Yes, I get that.

However there are SREs and DevOps engineers that are seemingly required for cloud solutions; and they cost more than sysadmins.

So, someone is lying somewhere.

Re:What We Lost with PHP and jQuery by r3trohack3r on Sunday June 01, 2025 @12:35PM (#44152073)
SREs have nothing to do with cloud solutions. You may have the wrong mental model here.

The profession grew out of observations made in catastrophic failures like Chernobyl.

They primarily focus on organization structures, communication structures, and responding to failures. At an engineering level they focus on meta stability - decoupling local failure from overall system stability to prevent local failures from cascading to catastrophic failures - and automated tooling to loop the right engineers into ongoing incidents.

The skill set is a side effect of operating at scale, where even brief catastrophic failures can result in hundreds of millions of dollars of losses; directly in revenue and indirectly to reputation.

Re:What We Lost with PHP and jQuery by jeremyjh on Sunday June 01, 2025 @01:14PM (#44152333)
That's what it meant 8 years ago. Now SRE is just a synonym for "devops" which now is a synonym for "sysadmin" in most companies. You won't have both devops and SREs in most orgs, and you won't have any devops doing dev work.
Re:What We Lost with PHP and jQuery by r3trohack3r on Sunday June 01, 2025 @01:24PM (#44152412)
If you’re fighting snake oil and buzzwords, you gripe isn’t with the cloud.

You can “buzzword” yourself into job security just as easily on a VM.

Re:What We Lost with PHP and jQuery by mattl on Sunday June 01, 2025 @12:18PM (#44151935)
Is it? $40 a month gets you a pretty beefy dedicated server.

EDIT: (I can't reply for a bit) Quick glance at https://www.hetzner.com/sb/ seems to suggest 64GB RAM and a full Intel i7.

Re:What We Lost with PHP and jQuery by Hobadee on Sunday June 01, 2025 @12:32PM (#44152049)
Define "pretty beefy", because in my research $40 will only get you something like 8 vCPU and 16GB RAM.
Re:What We Lost with PHP and jQuery by dijit on Sunday June 01, 2025 @12:56PM (#44152225)
for €48.75 you can get 12vCPU/64GB

https://www.hetzner.com/dedicated-rootserver/ax42/

But 8/16 is $95+ on AWS.

Re:What We Lost with PHP and jQuery by pragmatic on Sunday June 01, 2025 @12:45PM (#44152167)
What kind of IO?

That's where they get you.

Re:What We Lost with PHP and jQuery by mrweasel on Sunday June 01, 2025 @12:25PM (#44151991)
Sure, but so is running on AWS, Azure or GCP. Your on-prem bill tends to not run amok though. You don't wake up one day and get a bill for $100.000 for something that was accidentally deploy Friday afternoon.

People are starting to learn that cloud hosting isn't exactly cheap. It's great for quickly scaling, there's way better automation tools, e.g. Terraform, a lot of the complicated stuff is done for you, but it's not cheap.

37signals is running their own infrastructure, and it's cheaper than cloud.

Re:What We Lost with PHP and jQuery by pragmatic on Sunday June 01, 2025 @12:44PM (#44152161)
No you just shift bounded capex to unbounded opex.
Re:What We Lost with PHP and jQuery by ahofmann on Sunday June 01, 2025 @01:36PM (#44152497)
It just isn't. We are talking websites here. You can serve billions of requests from dirt cheap vps. Heck, I just saw a hetzner website, on a hosting plan for 20 € pumping out almost a terabyte of traffic per month. The database is included in the hosting plan.
Re:What We Lost with PHP and jQuery by const_cast on Sunday June 01, 2025 @04:04PM (#44153422)
It's pretty much always cheaper than going to cloud services.

The biggest thing I hear otherwise is "but salaries!". Okay, but you're just replacing your sysadmins with AWS devops people, who I can't imagine are cheaper.

Cloud isn't simple, it's very complex. You need just as many people and just as much knowledge to make it work.

Re:What We Lost with PHP and jQuery by Mikhail_Edoshin on Monday June 02, 2025 @01:36AM (#44156059)
Cooking your own food is technically less efficient; the per-meal costs are definitely higher than in a restaurant. But somehow eating in restaurants is more expensive.