News for hackers. Stuff that matters.
Re:Advent of Sysadmin 2025 by Wilya on Monday December 01, 2025 @06:45AM (#46106236)
In full-cloud environments, in small/middle companies I've worked at:

Developers handle 1). Devops handle 2)/3)/5). Nobody does 4)

Re:Advent of Sysadmin 2025 by f1shy on Monday December 01, 2025 @08:03AM (#46106917)
Thanks. That is an interesting insight into the current reality. I assume the developers take care of optimization of queries; set up indexes and development of schemas and DB backups is handled by devops.

I must say, again I thought (I read it somewhere?) DevOps should take care of the constant battle between Devs and Operations (I've seen enough of that in my times) by merging 1 and 2 together. But it seems just a name change, and if anything, seems worst, as a (IMHO) critical and central component, like the DB, now has totally distributed responsibilities. I would like to know what happens when e.g. a DB crashes because a filesystem is full, "because one developer made another index, because one from devops had a complaint because X was too slow".

Either the people are extremely more professional that in my times, or it must be a shitshow to look while eating pop-corn.

Re:Advent of Sysadmin 2025 by friendzis on Monday December 01, 2025 @09:49AM (#46108094)
> DevOps should take care of the constant battle between Devs and Operations

In practice there is no way to relay "query fubar, fix" back, because we are much agile, very scrum: feature is done when the ticket is closed, new tickets are handled by product owners. Reality is antithesis of that double Ouroboros.

In practice developers write code, devops deploy "teh clouds" (writing yamls is the deving part) and we throw moar servers at some cloud db when performance becomes sub-par.

Re:Advent of Sysadmin 2025 by sgarland on Monday December 01, 2025 @07:34AM (#46106678)
Nobody does 4 until they’ve had multiple large incidents involving DBs, or the spend gets hilariously out of control.

Then they hire DBREs because they think DBA sounds antiquated, who then enter a hellscape of knowing exactly what the root issues are (poorly-designed schemata, unperformant queries, and applications without proper backoff and graceful degradation), and being utterly unable to convince management of this (“what if we switched to $SOME_DBAAS? That would fix it, right?”).

Re:Advent of Sysadmin 2025 by avhception on Monday December 01, 2025 @07:04AM (#46106387)
Can confirm: that's exactly what we do.