You could call it that. The most direct analogy is RDP, or even a kvm. It's a remote session to another machine, but under the hood it's using the fast and efficient video codecs, h264 or hevc. It's also good about piping audio from the remote machine to whatever you're using locally.
I'm also hoping to dump windows. I spent a week trying to get my usb interface working with guitar rig running in wine bottles. I was getting nowhere with it just fell back to using the windows box remotely.
I'm in a similar situation: I have to keep a windows box around for specific audio tools and interfaces. A nice thing I've discovered is Sunshine (lizardbyte) and Moonlight. Sunshine is the desktop streamer that runs on the windows box, Moonlight is the client you run on the linux laptop (or android or whatever) to connect to Sunshine. I find it to be a nice solution for keeping the windows box easily accessible from my main displays/kb/mouse which are always tethered to the linux laptop. Thia streaming setup feels a lot more natural than RDP, and it's especially useful if you need to handle any video on the windows box. The main use case is video games, so there is that too.
Yep, same. I would add that if you get a compatible usb sata enclosure and run the OS off that the performance improvement is tangible, but i still felt it wasnt worth running nextcloud this way. Even on a pentium nuc i feel this just barely put nextcloud over the acceptable threshold.
I definitely found many, maybe even most of the characters bordering on comically corny. But i hadn't read anything like it regarding the core stories and concepts, and those got the hooks in me. Maybe for a bit i was holding my nose to keep moving through the story, but at some point i just didnt care and had to read all three books, and in the end they're still a dear favorite. If the underlying story isn't doing it for you, you're only crazy if you force yourself to keep reading it.
i ran this setup for years! One controller, three worker nodes, all Pi4b's. Someone mentioned that 4gb would be rather limiting; it certainly can be, but I never hit the ram ceiling. For me, disk writes and cpu were the noticeable constraint. In my first iteration I was using the fastest sandisk extreme pro whatever sd cards were at the time. My second iteration was running all hosts on usb-sata enclosures, and this was a huge improvement. I really can't recommend that route enough. If you can commit to a little cable management and maybe figure out something clean for stacking or standing the enclosures, it doesn't have to look terrible.
Regarding matching hardware, for a year I ran an old i5 lenovo thinkpad as just another worker node. It was fine, and was a pretty useful experience in running a cluster with mixed architecture. The only hiccups were those that come with a headless laptop setup. Sometimes rebooting could be dicey, stuff like that.
The only databases I was running at the time were sqlite (for the various *arrs). These would corrupt every few months, but these were not running on the sd cards, but on ssds and mounted over nfs. So yeah, don't go running sqlite over nfs.
edit: I imagine the warning about not running databases on the cards are about prematurely wearing out the cards. Seems like there are a few pi-oriented projects that lean on sqlite, though, so I'm not sure.
edit: Also just remembered that I experimented with running one node on one of those ssds that are pressed into the form factor of a usb stick. Again, sandisk extreme pro line, 128gb. I ended that after getting total freezes every few weeks. I can't say whether it was a faulty device or some incompatibility at play. I never did proper benchmarks with this against the ugreen sata usb enclosures, but it certainly did not feel any faster than the enclosures.