Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It <em>is</em> possible to do use management in an eventually consistent data store. We do it. It works under the following assumptions:</p> <ol> <li><p>Conflicts shouldn't happen and when they do there's a clear path to conflict resolution. If the account ID is a person's email address, then if two separate people try to register under the same email there's a bigger problem here. What we do in this case is block both new accounts as soon as the conflict is discovered and send an email to the address in conflict explaining to the user that there's an issue (possible fraud). You can either ask the user to reset to the account or ask them to contact support.</p></li> <li><p>Repeated access by the same user within the timeframe in which the data is inconsistent go to the same replica. For instance, if a person just registered and the next request is a login, you must validate that login against the data replica where the new registration details exist. So if the eventual consistency is due to multiple data centers in different geographic locations and under normal conditions a request goes to the closest data center geographically, you're OK.</p></li> </ol> <p>There are some edge cases, such as if a user registered against one data center, then that center crashed, and now the user cannot login even though he still can see the application - served from some other data center. You can calculate the expected frequency of this case based on your number of daily new users and average data center downtime. Then decide whether it's worth worrying about one user in a (million/billion/whatever your number is) having a problem and possibly contacting support. I faced the same decision not long ago and decided that from a cost-benefit perspective the answer is no.</p>
    singulars
    1. This table or related slice is empty.
    1. POIt is possible to manage users/identities in a data store that exhibits eventual consistency?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USElad
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIt is possible to manage users/identities in a data store that exhibits eventual consistency?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks +Elad. That's a pretty helpful answer. To add to it, I've also come the the conclusion that it would be possible to reduce the impact of point 2, by delaying account finalization. This could be done by say emailing a link to verify the user's email address. The account would be created, but not activated. At the point when activation occurs if two accounts with the same email exist then resolution can take place.
      singulars
      1. PO
      1. USJBowen
    2. COFurther, you can minimize the impact of eventual consistency on platforms like Cassandra by using a higher consistency level for consistency-critical information like accounts, while leveraging the speed of eventual consistency for information where it is less important to be up-to-date. See ConsistencyLevel @ http://wiki.apache.org/cassandra/API
      singulars
      1. PO
      1. USChris Shain
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload