Confirmed users
908
edits
Identity/PersonaProfileServer: Difference between revisions
Jump to navigation
Jump to search
→Questions
| Line 16: | Line 16: | ||
= Questions = | = Questions = | ||
* What is the maximum amount of data that can be stored per user? | * What is the maximum amount of data that can be stored per user? Depends on number of emails and max size | ||
* Are we storing arbitrary keys or are only well defined keys going to be allowed? | * Are we storing arbitrary keys or are only well defined keys going to be allowed? No | ||
* How often is this data accessed? What is the write pattern? What is the read pattern? (only accessed at registration? not written often?) | * How often is this data accessed? What is the write pattern? What is the read pattern? (only accessed at registration? not written often?) | ||
* How are we handing back the data? | * How are we handing back the data? | ||
* What kind of database will we use? | * What kind of database will we use? MySQL? | ||
* What does the API look like? | * What does the API look like? | ||
* If we launch as an alpha service, how do we handle migration from alpha to beta to release? | * If we launch as an alpha service, how do we handle migration from alpha to beta to release? Not a problem as long as we consult with ops while designing the labs prototype. | ||
* Can other services be attached to this DB? | * Can other services be attached to this DB? Not for now (even though it looks like contacts maybe) | ||
* What is our timeline? What is the data that we are going to use to decide when this is going to come out of labs and into production? | * What is our timeline? What is the data that we are going to use to decide when this is going to come out of labs and into production? 2012Q1 ;) | ||
* What is the data SLA? Where does data need to be backed up? | * What is the data SLA? Where does data need to be backed up? | ||
* What happens when the profile server is down? Does BrowserID sign-in depend on it? | * What happens when the profile server is down? Does BrowserID sign-in depend on it? You can still login but there's some kind fallback design/graphics for the moocards. | ||
* Can we push image resizing / optimizing to the client? | * Can we push image resizing / optimizing to the client? No all of it, but hopefully some of it. | ||
== Questions continued == | == Questions continued == | ||
* Find out number of emails per user | * Find out max and average number of emails per user [petef] | ||
* Decide on a maximum image size | * Decide on a maximum image size [skinny] | ||
* Run the moocard idea past skinny | * Run the moocard idea past skinny [skinny] | ||
= TODO = | = TODO = | ||