canmove, Confirmed users
640
edits
Services/Sync/NextGen: Difference between revisions
Jump to navigation
Jump to search
→Product Questions
| 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. | ||
** | ** Cost estimates and recommendations coming from Bob soonish. | ||
* What is the user expectation for data availability, above and beyond "the bits in the cloud don't go away"? | * What is the user expectation for data availability, above and beyond "the bits in the cloud don't go away"? Durability would mean we don't lose your bookmarks if you do nothing, but beyond that users might want to get back their bookmarks after they accidentally deleted them all. To what extent should backup/versioning etc. feature in our roadmap? | ||
* Is there a per-user uptime requirement? (Asa, mconnor) | * Is there a per-user uptime requirement? (Asa, mconnor) | ||
| Line 72: | Line 72: | ||
** How would you define uptime requirement? A see many options. At any time N% of users have Sync working for them. Sync is working for any user N% of the time. Sync is available to a particular user N% of the time they attempt to connect to it. etc. | ** How would you define uptime requirement? A see many options. At any time N% of users have Sync working for them. Sync is working for any user N% of the time. Sync is available to a particular user N% of the time they attempt to connect to it. etc. | ||
* How should migration be messaged? Is it sufficient to have a note on the newly set-up device saying that your other devices need to be upgraded? A non-fatal notice on the old devices (requires work | * How should migration be messaged? Is it sufficient to have a note on the newly set-up device saying that your other devices need to be upgraded? A non-fatal notice on the old devices (requires work on Sync 1.1)? A fatal error on the old devices? | ||
* 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! This is very relevant to mmayo's team, and affects the operational timeline. | ||
* Do we want the PIdP to be featured as browser-wide UX, or only as part of Sync? (Asa) | * Do we want the PIdP to be featured as browser-wide UX, or only as part of Sync? (Asa, Karen) | ||
** This requires thought for technical delivery on mobile, too. | ** This requires thought for technical delivery on mobile, too. | ||