Riak for user information?
sean at basho.com
Wed Jan 7 10:06:43 EST 2015
I disagree with whoever said that. User information (like a profile or
account) is some of the easiest to implement with eventual consistency,
namely because it would be rare to be in conflict (only a single actor
updating), and conflict resolution can be performed trivially without
intervention or presented to the user in straightforward ways.
If you're concerned about ensuring uniqueness of user identifiers, you can
go with any one of a number of workarounds like UUIDs, "Snowflake" IDs, and
cryptographic hashes/tokens, or go the slow route and ensure it via strong
The benefits of using Riak for this sort of data are the typical ones: high
reliability and durability, global availability (if using Riak Enterprise),
and simplified operations. Basically, barring problems in other components,
your users will almost always be able to view and edit their profiles.
On Wed, Jan 7, 2015 at 7:49 AM, xu xiut <xiut.xu at gmail.com> wrote:
> I've heard several times now that key/value stores aren't ideal for
> storing user information. Why is this true?
> Does this apply to Riak even with strong consistency in 2.0?
> riak-users mailing list
> riak-users at lists.basho.com
Sean Cribbs <sean at basho.com>
Sr. Software Engineer
Basho Technologies, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the riak-users