Size and noise I guess.

Thanks dude. I’m not sure what I’m looking at though. As I mentioned in the top post, I’m new to this and it’s not my hobby.

You listed hardware, but gave no context how good it is for my needs - I think that’s why you got downvoted.

Thank you~!

I want to spend as little time on it as I can. Then I’d like to minimize the initial cost of it, or at least cost of exploitation.

I’m fairly busy with my hobbies (Lego and Arkham Horror LCG), so I’m looking for the solution. I’d rather spend more money than more time.

On the other hand, if I waste money on garbage I’m going to be cross and do it from the scratch again, so I’m trying to hedge my options before I commit - if that makes sense.

Thank you for the tip. Regions sucks, its 350$ for me :(

Edit: and its 195 through gmktec website

Thank you.

Next week 2 month / year when you decide to run something else or more, not so much.

Could you maybe give me an example of what that could be? I might be not knowledgeable enough about what I could do with it.

I don’t want to hear the fans

To be precise, only when not in use. When it’s working then yeah, its gonna cool down somehow.

Thank you, but I don’t want to keep my desktop running. The cooling noise, the electricity. Did I mentioned the fans? They are quiet but I can hear them, I want something that goes silent and wakes up when needed.

The answer is impossible to answer until you tell us more about your needs. Better choice considering what?

In general, untill you have terabytes of data or a significant amount of traffic (operations per second) database choice does not matter and you should be using cheaper option, where the cost should be assessed as a derivative of price of hosting, cost per operation, cost to deliver (how familiar you are with it).

When you have significant amount of data or traffic - only then you should worry about database kind or language. Until then this could be a premature optimization.

I heard from a game dev that UE isn’t an engine, but a framework. That means it doesn’t give you optimized, opinionated code, but gives you more “freedom” - yet forces each dev team to optimise by themselves.

Which they either don’t or do poorly.