Log in
| 1 | ||
| 1 | ||
| 1 | ||
| 1 |
So i got myself set up using oracle, and there is a lot of chatter online about mixed results. I could not get the shape i wanted so im now on 1gb with OCPU count: 1 with their VM.Standard.E2.1.Micro. There is a version above that with flex and that has i think 4 ocpu and is 4 gb memory, i dunno, but i couldn't get that to build. Currently using putty to ssh into it and setting up nginx. its taking a while, so i dunno if i'll get that all done tonight - i still have to make my holding page. But all in all, not bad.
One thing I see almost every beginner face is a substantial over estimation of the resources they need. It takes a lot of traffic to consume any significant cpu. There is a good argument for being duel core at least rather than single core because there are a few common things in webdev that can burst a cpu like password hashing and it's good if another core can still handle traffic. Memory is really for database and for less memory efficient languages like nodejs to a lesser extent. Unless you have a huge database there is no benefit to having more memory than you actually need as long as you can stay out of swap space.
Basically my advice is don't sweat the scale. "Do I need more?" If you are just starting out and things are running the answer is, no, no you don't. Remember that web-dev is one of the lowest demand activities a computer will ever see. That's made up for later by sheer user scale if you are running reddit. You may remember that old voat ran into cost issues with scaling their tech. That's not because webdev is expensive. It's because they were morons. That site even at it's peak could have run for $40 a month. They were spending thousands. Why? Because of instead of learning how to access a database reasonably and learning how to make cheaper database/technology selections (Azure and SQLserver), they just threw money at it. So allowing yourself to use far more resources than you need from the start can really lead to some bad habits.
One tech practice that is becoming increasingly popular if not a full on tech standard that I wish I had gotten into from the start is not living on one VM too long. Deploy often is the mantra. One upside to doing that, especially when you are new, is the opportunity to associate different VM scales with real world outcomes though actual experience.
Good advice. Yeah, this is why im going with the Oracle to start out with. Its free, its can deploy my website while i build it up and i dont have a rolling cost associated with that. Im also trying to optimize due to the limitations, so that means using ngnix vs apache and so on. Im not expecting any traffic other then web indexes, and once i have content for that page and i see an increase in traffic, then i can scale - move to a dedicated hosting environment. eventually i would like to self host so thats a thing. In the game "dont starve together" they use an approach to multiplayer where their lobby is just a single page web site that lists other people who are/want to play. So you click that and it automates the process to connect to each other for either distributed networking or one pc set as the mini server for that game session, i dont know if they are using a nat punch through or whatever, but that is how that connection happens. I plan on doing something similar for my game, as then i dont really have a heavy load that i have to host, unlike say, running a minecraft server.