2 ms·
> a year or so ago, that was 64GB RAM per database for their Mongo instances. That's definitely more than $1000 a year's worth. You are mixing data, memory and
by beagle3 15y ago
> a year or so ago, that was 64GB RAM per database for their Mongo instances. That's definitely more than $1000 a year's worth.
You are mixing data, memory and processing power. In the case Amazon crashes and burns, they need that CPU+Ram+bandwidth etc. near the data.
But to just keep a copy of the data (not available online) they don't need a really beefy server -- just store all the updates from a node, and replay them later at your leisure. 5400rpm will often be fast enough for this purpose (of course, you would need days to recover in this setup ... but that might be ok if past data is not needed online)
Take twitter or foursquare for example: They need everyone's most recent max(4, tweets/checkins in the last day) available online at any given time. But if last years' tweets/checkins are not available online when the system is degraded in case of backup restoration etc -- that may be acceptable.
- deleted 15y ago[deleted]