3 ms·
Unless you're doing something stupendously horsepower- or data-intensive, don't use a cloud (roll-your-own or outsourced) at all. Sit a spare PC under a desk so
by taneq 10y ago
Unless you're doing something stupendously horsepower- or data-intensive, don't use a cloud (roll-your-own or outsourced) at all. Sit a spare PC under a desk somewhere and run your servers/services on that. Once you figure out what you're actually doing and you know how your core technology scales, then you look at what's required to serve it to your target audience.
- sokoloff 10y agoOr connectivity intensive. AWS (and other cloud providers) provide a network that is difficult/impossible to compare to a "PC under a desk somewhere". They're managing the daily deluge of DDoS attacks and you're paying for less than 0.0001% of that because a million other customers are sharing the burden.
- kuschku 10y ago> https://www.versatel.de/business/kompetenz/glasfaser/ausbau/ https://www.versatel.de/business/kompetenz/glasfaser/ausbau/ At only 7200€/month for a 100Gbps line, the network won’t be an issue in case of a DDoS for you anymore. DDoS’es over 100Gbps will be irrelevant anyway for you, because at that point your ISP will already getting issues.
- falcolas 10y agoAmazon absolutely can survive a DDOS attack. But can your wallet? AWS published a white paper on how to survive a DDOS on AWS that amounted to "out scale the attack." Doing that could very well be a business ending proposal right there. Sure, your website never went down, but now you have an infrastructure bill you'll have do do another round of funding just to pay off.
- sokoloff 10y agoI was more thinking of the DNS amplification and UDP flood type of attacks that are transparently handled by a cloud provider, but even for an application attack, you still have a choice to let your site go down rather than scale up infinitely. (You can cap the scaling.)
- avifreedman 10y agoThey do manage those - though mainly for protecting themselves, not the point customer being attacked. In AWS the people I've talked to recently as well as historically say you'll get pretty uniformly rate-limited? vs. actually doing per /32 DDoS mitigation type limiting. Has your experience been different (for volumetric attacks)?
- sokoloff 10y agoOur experience has been that the "collateral damage to us" DDoS attacks vanished entirely from the "set of things we think about" which was not at all true in some of the colo's we were in. In terms of application-specific attacks, we have used proxies in AWS to mitigate attacks against our colocated servers from time to time. AWS handles some of the volume and some of the types of attack traffic, and we scale and cache to handle others. This was much cheaper and easier than some of the Prolexic type solutions. Agree that they aren't doing anything specific on a host or customer basis, but just inherent in protecting all of their customers, some of the specific problems also go away.
- avifreedman 10y agoAbsolutely agree that collateral damage vs many small-mid-sized hosting providers is 0 in Amazon, though you do still have to deal with the normal 'noisy neighbor' problem by re-creating instances in a different neighborhood.
- simpleigh 10y agoI don't agree with this strategy. A spare PC under a desk might work perfectly for years without any trouble. Alternatively you might spill coffee over it next week and destroy the server - and your business. If you don't know how you'll need to scale then chuck up a `t2.nano` instance on AWS and use that. In return for a tiny monthly cost you get: - solid network connectivity - disk snapshots for backups - geographically redundant storage (S3) for static resources so you can survive the server hosing itself - monitoring of CPU load / status / disk usage - the ability to scale the server up vertically with the click of a mouse and 60 seconds' downtime - (with a tiny bit more work and cost) automatic scaling so you cope _automatically_ if the server falls over or load increases