News for hackers. Stuff that matters.
Re:DevOps is a failure by onion2k on Sunday June 26, 2022 @05:41PM (#31888306)
2005 Your app takes some user data, stores it in a database, and presents a filtered view of it to the user on request.

2022 Your app takes some user data, stores it in a database, and presents a filtered view of it to the user on request.

Re:DevOps is a failure by _vertigo on Sunday June 26, 2022 @05:52PM (#31888409)
Well if that’s all you’re doing in 2022, there’s nothing wrong with deploying your code and grepping logs over ssh. Bash scripts and offloading some of the complexity of management to AWS (e.g. use autoscaling) goes pretty far
Re:DevOps is a failure by onion2k on Monday June 27, 2022 @06:28AM (#31892637)
In 2002 I built a website that got about 3m page views a week, with about 50k concurrent users, and a whole bunch of fun things like payments, outbound email, etc. It ran on a single server.

Since then I've working on things that use several servers, things that use no servers with edge functions instead (which have servers, but still), and that use autoscaling across lots of servers.

No doubt some businesses need autoscaling but most don't. It definitely shouldn't be something you reach for before you actually anticipate a need for it.

Re:DevOps is a failure by HelloNurse on Monday June 27, 2022 @04:30AM (#31891950)
Autoscaling? Do you mean facing so much cloud management complexity that it invites automation, in order to spend more money for a herd of excitingly ephemeral server instances than for a reasonably overprovisioned boring actual computer?