canmove, Confirmed users
640
edits
Services/Sync/NextGen: Difference between revisions
→Product Questions
No edit summary |
|||
| Line 64: | Line 64: | ||
* What degree of durability is required for data stored on the service? (Asa, mconnor) | * What degree of durability is required for data stored on the service? (Asa, mconnor) | ||
** mconnor: This is going to be a budget question. It needs a cost/benefit tradeoff from mmayo's team. From prior discussions, more than 99.9999999% will be much more expensive, but 1 in a billion feels pretty okay. | ** mconnor: This is going to be a budget question. It needs a cost/benefit tradeoff from mmayo's team. From prior discussions, more than 99.9999999% will be much more expensive, but 1 in a billion feels pretty okay. | ||
** Lots more expensive. Lots more. | |||
* What is the user expectation for data availability, above and beyond "the bits in the cloud don't go away"? That is, a user doesn't give a fig about that most of the time; they want to get back their bookmarks after they accidentally deleted them all. To what extent should backup etc. feature in our roadmap? | * What is the user expectation for data availability, above and beyond "the bits in the cloud don't go away"? That is, a user doesn't give a fig about that most of the time; they want to get back their bookmarks after they accidentally deleted them all. To what extent should backup etc. feature in our roadmap? | ||
| Line 74: | Line 75: | ||
* To what extent will we be pushing this feature? Privileged account + durable storage implies backup, and if half a billion users sign up, we need to reflect that in capacity planning! | * To what extent will we be pushing this feature? Privileged account + durable storage implies backup, and if half a billion users sign up, we need to reflect that in capacity planning! | ||
* Can we decouple 2.0 and ID? Deploy 2.0 with a token server talking to LDAP. Simplifies migration. | |||
== Technical Questions == | == Technical Questions == | ||