3 ms·
Migrations like these take time and happen step by step. First you can try to replicate some data and move read instances. After that step by step the rest. I
by pojzon 8y ago
Migrations like these take time and happen step by step.
First you can try to replicate some data and move read instances. After that step by step the rest.
Its really not possible to do that overnight or months even.
Fyi: im currently migrating twice the Twitter size one in the world infrastructure from aws to azure now.
- tpetry 8y agoIsn‘t exporting 600TB of data from aws ridicously expensive?
- deleted 8y ago[deleted]
- asaddhamani 8y ago600TB would come out to around $50000 which for Twitter is peanuts. This is their bandwidth pricing though but I guess they'd use snowmobile export (if that exists?) instead.
- gervase 8y agoFor reference, 300PB (the amount referenced in the article) using the same pricing would cost $25M. Still might be a reasonable one-time cost for migration for a large corporation, though, even disregarding the "bulk" rates they'd see at that scale.
- teej 8y agoAWS Snowmobile cost is $0.005/GB per month which comes out to $1.5M/month for 300PB for however long the data is on the truck.
- detaro 8y agoTwitters number is in PB, not TB. At that scale, assume that none of the normal pricing and procedures apply.