4 ms·
At around the same time I was working at a startup in London. We had two sizeable clusters - Hadoop and Cassandra - neither of which was conveniently elastic,
by Jedd 5y ago
At around the same time I was working at a startup in London. We had two sizeable clusters - Hadoop and Cassandra - neither of which was conveniently elastic, but were located on EC2. We had sundry other instances, but those were the major culprits for our ~ £25,000 / month.
It took me about a day to scope out a BOM that would well surpass that (maybe a year's expected growth) of whitebox server gear, and get some quotes from nearby co-los.
IIRC hardware capex was about £15,000, and monthly rack + network something around £3,000. We relocated within a few weeks.
One small bonus was predictable & consistent performance -- back then, the EU-west EC2 offerings were extremely sensitive to noisy neighbours, and our benchmarks never gave anywhere near the same results twice.
I think for genuinely elastic loads, or if you're really addicted to some vendor-only services, it certainly makes sense. I suspect most customers are overly optimistic about how elastic their requirements are, and their stack can be.
- gravypod 5y agoI've had the opposite experience where others didn't see the cost savings, and also performance improvements, as a benefit. Some people get "scared" when you don't put things in the cloud. Meanwhile a last gen server with new SSDs running your applications on bare metal can outperform most EC2 instances and whatever networking cross connects at your local DC are available will get you higher bandwidth, lower latency, and more throughput for way less than AWS.