4 ms·
As far as my memory goes, iCloud features at least 99 partitions. The 99th of which is the "staging" partition where the iCloud employees' data lives. All part
by therein 7y ago
As far as my memory goes, iCloud features at least 99 partitions. The 99th of which is the "staging" partition where the iCloud employees' data lives.
All partitions are more or less separated and shouldn't affect one another. For that reason, it probably wasn't you that broke the whole system.
Even the Cassandra they use for metadata storage is partitioned and separated.
- cordite 7y agoSo, it is fair to say this is just the full stack (endpoints, databases, etc) being sharded consistently?
- therein 7y agoYup, correct. The whole stack is consistently sharded. They should be sharing little to no machinery at all and only a handful of people are able to use the "migration" tool to force your account from one partition to the other. What had struck me as an interesting vector back when I was involved with iCloud was how this ability could be used to move an account from a production partition to the staging partition as staging partition has unique debugging and tracing capabilities. When an employee joins iCloud, their account is often moved from the production partition to the staging partition using this tool. Technically it should be possible to take any iCloud account and move it to this partition and use the slightly modified code in there to gain access to the contents of the account.
- deleted 7y ago[deleted]
- deleted 7y ago[deleted]
- photojosh 7y ago> The 99th of which is the "staging" partition where the iCloud employees' data lives. As in, if there's a failure in iCloud code, it'll affect employees who worked on that code before everyone else? Good use of dogfooding!