Comment by diggan 10 months ago
I don't think you'd have to consider migration all the data from Pivotal, but lets assume 10% just in case? Lets say that's 100TB in total (on disk), which you could host with 10x storage boxes from Hetzner, 24 EUR each per month, so 240 EUR in total, which includes 10 unmetered connections (1 per box).
Obviously I meant 10% of all customers would hypothetically migrate from Pivotal to this new imaginary service, not that 10% of the data from each customer would be migrated... So 100% of the data migrated from 10% of the Pivotal user base, pretty generous assumptions I think.
> Obviously I meant...
Respectfully: if it was obvious, I wouldn't have come to the conclusion I did and written up what I wrote.
> So 100% of the data migrated from 10% of the Pivotal user base...
Yeah, maybe. I don't know how large the slice of the Pivotal Tracker userbase you'd be able to retain even if you had a perfect clone. I bet it would be notably larger than you imagine it would be... it's my understanding that it has some pretty rabid fans that used it.
> Respectfully: if it was obvious, I wouldn't have come to the conclusion I did and written up what I wrote.
Sorry about that, I think I assumed some familiarity with moving data around/migrations, and moving 10% of a customers data around from a legacy service to new service wouldn't make much sense in that context.
> I bet it would be notably larger than you imagine it would be
I think being able to capture 10% of existing users is already a very large guess, realistically it would be closer to 1%.
But, without any numbers from Pivotal and actually trying to launch a cloned service, all we can do is guess :)
> Respectfully: if it was obvious, I wouldn't have come to the conclusion I did and written up what I wrote.
I dunno, that felt obvious to me. Both the idea that you’d somehow manage to get all customers to migrate to your new service, as well as that they’d migrate only 10% of their data sound preposterous.
> I don't think you'd have to consider migration all the data from Pivotal...
I do. You might not have demands to migrate all data from all of your potential customers, but far, far more people than you might expect treat their issue tracking system as a system of record and external memory for a HUGE assortment of things.
One hugely (and obviously) useful query chain that such a system answers is "Hey, this customer problem sounds familiar. Did we investigate it before? Did we solve it? If so, how? If not, why not?". For long-running projects, it is impossible to select the correct 10% of data to retain to also retain the ability to reliably -er- service those query chains.