“Yeah, my dad is a billionaire with a rocket car and he invented toothpaste!”
There was a girl who lived down the street from me at one point who swore to the whole neighborhood that her dad sued the local Burger King for millions of dollars because he found rat turds on his burger. No, Victoria, we all live in a trailer park in singlewides, that BK didn’t even have millions to take, come on now lol.
At one of my previous gigs our boss was big on the “double the devs/half the time” mentality. Our favorite response was 9 women can't make a baby in 1 month
That makes a lot of sense and where I’m leaning towards as well
While my homeserver still has plenty of resources to spare, I see a lot of them going towards multiple DB containers. It’s nice for “segregating” the containers, but backups are also a pain, gotta plan backups/restores for multiple DBs
Same story with an s3 (well, minio) instance running. Seems like it would make more sense to centralize DB and file operations and having different services talk to them. Then if I ever needed to move them into separate servers, it wouldn’t be as big a move.
Thanks!