User formerly known as raginghungrypanda@lemm.ee

  • 1 Post
  • 52 Comments
Joined 6 months ago
cake
Cake day: June 4th, 2025

help-circle


  • I actually disagree, because I’ve both seen it everywhere and I also work mainly in dotnet, and when I’ve talked to people about option and result types, the first inclination is to have a .Value, but that defeats the purpose. I’ve done quite a few code reviews where I was essentially saying “you know this will throw, right? Use .Match or .Map instead”.

    I think the imperative programming backgrounds encourage this line of thinking, since one of the first questions I’ve gotten is “how do I get the value out of an Option? I’m 100% sure it’s there.” And often, surprise, it wasn’t.









  • Id say don’t go down the distributed software route just yet. An option is to keep the NAS and set up a new computer with your router or whatever handling dns to it for services. You should be able to use NAS storage over the network. It’ll be slower, but let’s say you put your database on the big one, then it shouldn’t be so bad since you’ll just make database calls to it.

    There are a lot of options. I’m currently learning kubernetes and all that stuff is a big learning curve, so avoid that stuff.

    My thoughts: you can do some simple dns load balancing between the two servers at whatever level is handling that. Set up a database on the storage server and let the new computer communicate to it over the network.