Very high latency, though. Great for some use cases, useless for others.

It wasn’t named by IT people, though. It was named by academics. And it’s not about using computers, it’s about computing. Computer science is older than digital electronics.

Besides RAM, what resources do you think you’re saving? Not CPU cycles or IO ops, because you’re processing the same amount of DB queries either way. Not power consumption, since that isn’t affected by RAM utilization. Maybe disc space? But that’s even cheaper than RAM.

Or more importantly: the extent to which you can self-host out of sheer luck and ignorance like you suggest is very limited. If you don’t want to engage with a minimum amount of configuration, you might bump into security issues (a much broader and complex subject) long before any of the above has a material impact.

You’re mischaracterizing what I said. My point is that running multiple DB processes on a server isn’t going to have a significant impact on system load, if all other factor are kept constant.

You seem to be obsessed with optimising one resource at the expense of others. Time is a limited resource, and even if it only takes 5 minutes to configure all of your containers to share a single db backend (it will take longer than that even if you just have 2), you’re only going to save a few MB of RAM. And since RAM costs roughly $2.5/GB (0.25 cents/MB) your time would have to be worth very little for this to be worthwhile.

On the other hand, if you’re doing it to learn more about computers then it might be worthwhile. This is a community of hobbiests, after all…

Neither, I’m trying to explain that you don’t need to know the implementation details of the software running on your server to backup the entire thing.

Where are you getting that from? The fastest and easiest way to back up any server is a full filesystem backup, especially if you’re using something like zfs or btrfs.

I’m saying this based on real world experience: after a certain point you start to see deminishing returns when optimizing a system, and you’re better off focusing your efforts elsewhere. For most applications, customizing containerized services to share databases is far past that point.

Do you have the data to back that up? Have you measured how much of an impact on system load and power consumption having 2 separate DB processes has?

Roughly the same amount of work is being done by the CPU if you split your DBs between 2 servers or just use one. There might be a slight increase in memory usage, but that would only matter in a few niche applications and wouldn’t affect environmental impact.

For most applications the overhead of running a second DB server is negligible.

I write software for a living, and have worked with all 3 database options in the past. I don’t know what DB backend my nextcloud server is using, nor do I care.

Not me, I’d rather work on a clean code base without any slop, even if it pays a little less. QoL > TC

The high school I went to let seniors who had jobs leave at noon. They took the core classes but not electives and were allowed to graduate as long as their boss confirmed that they were working and not just skipping class. It was legal.

Yeah, the whole situation is definitely eyebrow raising.

I knew more than a few 17 year olds who dropped out of high school to work full time. One was emancipated. A few eventually got their GEDs. It’s not an easy life, but it’s reality for a lot of people.

If he’s capable of handling that level of responsibility I don’t see any reason he shouldn’t be allowed to. If he’s not capable, then the only person being harmed is his employer. Only thing I’m concerned about is whether or not he’s being compensated fairly.

Child labor? He’s a senior in high school, it’s common to have a job at that age.

There are a lot of highly paid software devs who started with no connections or college degree. This might be the hardest time to enter the field as a junior, but it’s definitely not full of nepo babies. You must be thinking of finance/law.

Debugging code is always harder that writing it in the first place. If you make it as clever as you can, you won’t be clever enough to debug it.

My team uses the -Werror flag, so our code won’t compile if there are any warnings at all.

You don’t need unsafe to write vulnerable code in rust.

https://github.com/Speykious/cve-rs

Yeah, I missed the custom allocator at first. I thought I deleted my comment fast enough, but I guess you were faster. :)