Confirmed users
358
edits
Services/KeyValueStorage: Difference between revisions
Jump to navigation
Jump to search
→Namespacing
| Line 84: | Line 84: | ||
Some apps might find it useful to have an application-wide namespace, but I think it should be avoided if possible - as I understand it, much of our infrastructure is predicated on being able to shard on user-id to scale out storage and processing needs. | Some apps might find it useful to have an application-wide namespace, but I think it should be avoided if possible - as I understand it, much of our infrastructure is predicated on being able to shard on user-id to scale out storage and processing needs. | ||
Note that the HTTP api doesn't specify the user in the URL, since this information will be provided in the auth credentials along with the request. Should we put it in the URL anyway for consistency? | |||
=== Basic Key-Value Storage === | === Basic Key-Value Storage === | ||