Confirmed users
358
edits
Services/KeyValueStorage: Difference between revisions
Jump to navigation
Jump to search
→Planning Questions
| Line 10: | Line 10: | ||
*handling of concurrent edits, conflicts? | *handling of concurrent edits, conflicts? | ||
*bulk insert, update or delete operations? | *bulk insert, update or delete operations? | ||
Durability | |||
* flush to disk on each write? | |||
* in-memory with periodic flush in background? (e.g. MongoDB) | |||
* application-configurable? | |||
Crypto | Crypto | ||
| Line 30: | Line 36: | ||
*Build a SyncStorage plugin that stores data in the KVStore? | *Build a SyncStorage plugin that stores data in the KVStore? | ||
Management features | |||
*explicit TTLs? | |||
*built-in quota system? Will be more efficient than simulating it at a higher level. | *built-in quota system? Will be more efficient than simulating it at a higher level. | ||
And importantly, how many of these things will we let each application decide for itself? IOW, how may knobs will there be for apps to fiddle with? | |||
== Strawman Proposal == | == Strawman Proposal == | ||