8 ms·
it's probably not included because keeping your production server outside of a datacenter is kind of a silly idea. you save some money, but you don't have the
by notatoad 15y ago
it's probably not included because keeping your production server outside of a datacenter is kind of a silly idea. you save some money, but you don't have the cooling, the power conditioning, the network redundancy, or the security of a proper facility.
- rhizome 15y agoI've been running my own servers out of my closet right here, on my ADSL (though formerly business SDSL) line, for over 10 years. A PC on the floor is fine to start with. It can run MySQL, your framework of choice and give you something you can show people. Evidence: I ran and wrote the backend to a site, starting with two PCs on a DSL line, before ultimately being acquired by EA (stopover at Rackspace). For a couple hundred bucks (2x 3GHz 4G RAM) you can have a zillion times more flexibility than any cloudy free plan (Heroku, etc.).
- ricardobeat 15y agoWhat kind of uplink do you have? An app that starts getting into the thousands of users will quickly saturate a normal ADSL line (1-2mbps up), and an SDSL/T1 connection is many times more expensive than a remote dedicated server.
- rhizome 15y agoWell, you move to hosting before you have thousands of users, silly! I'm talking POC/MVP stuff. My uplink is something like 384Kbit, plenty for showoff purposes.
- adambyrtek 15y ago384kbit (48kB/s) is plenty? You are kidding, right?
- ricardobeat 15y agoThat speed guarantees you a load time of at least 5 seconds for the average HTML page (with a single visitor), assuming best conditions. Even shared hosting, which is almost free, will fare better than that.
- rhizome 15y agoOh do please supply the numbers you're working with.
- ricardobeat 15y ago300kb in an average HTML page, 47kb/s top transfer speed. It's physics.
- _delirium 15y agoI suppose it depends on your use case, but I don't see those as necessarily worse failure modes than other options. For example, Reddit has in the past been down for >20 hours at a time with its cloud solution. With a local solution, you would want offsite backup for the catastrophic "building burned down" failure mode, but most local failures can be solved in that kind of timeframe with the "drive to Frys, buy new server, and restore from backup" recovery plan. Now if you can't afford any downtime, a local server is probably not a good idea, but then neither are many of the cloud alternatives. Also depends on size, of course; one or two local servers is a more reasonable proposition than 35 servers randomly thrown under desks. (Though the "so uh, does anyone remember which room 'thor' is in?" moment used to be a classic startup rite of passage.)
- notatoad 15y agoreddit goes down because they abuse(d) the shit out of AWS. judging cloud hosting by their failures is pointless. EBS is not meant to be a large scale memcached server. i've done the "drive to fry's, buy a new server, restore from backup" type recovery. it sucks, you don't want to do it, but that's not what i'm talking about. if you're self-hosting at your office your run into all sorts of problems that datacenters solve. the cleaning staff at the DC will never unplug your server. you won't spill beer on it. if the internet goes down, they can fail-over to another connection, your office probably can't. the DC is closer to the backbone, giving your customers less latency. adequate cooling and smoother power means longer life for your hardware. and as you grow it's much easier to grow in a DC than having the server portion of your office gradually take up more and more space.
- azylman 15y agoJust curious, how has reddit abused AWS?
- SomeOtherGuy2 15y agoThey didn't. They just tried to store data on EBS volumes, you know, like they are supposed to. But EBS performance is very bad, and incredibly variable. So they would end up getting timeouts trying to write to the volumes, which broke their DB replication, which took the site offline for hours to re-replicate.