Micro services alone aren’t enough. You have to have proper observability and automation to be able to gracefully handle the loss of some functionality. Microservice architecture isn’t a silver bullet, but one piece of the puzzle to reliable highly available applications that can handle faults well

I vaguely remember reading a news story about a firefighter that did that a while ago.

My 4 host machines run debian (proxmox). I have a lot of different guest flavors running though, debian, fedora, rocky, one old guest still running Ubuntu and even a mint sandbox machine.

I probably have a bit more complicated self host than others because I am using it both for my useful internal services (jellyfin, git, pihole, etc.) I also run a whole lot of services for learning, such as kubernetes and dns. Plus a whole lot of other mostly useless stuff that I only use to test different architectures or automations that come in handy as an SRE.

Dotnet core 3.x exists

Dotnet core 4 never existed because they wanted to make it the mainline dotnet… That means framework is retired and everything is now the slimmer multiplatform runtime.

I call it d-bag for short.

And that’s just to figure out how to save and exit.