Server-side JPAStorageService using an eventually consistent database

[Martin Haase]

Dear list,

we are about to investigate what happens if the current IdP's
JPAStorageService implementation will be connected to an eventually
consistent database cluster. This would mean

  * the IdP writes its storage record to one database node A,
  * some subsequent write or read event will hit another node A'
  * there is no guarantee that the storage record is already replicated
    from A to A'
  * the only guarantee is that information converges from A to A' at
    /some/ possibly later point in time
  * there might arise conflicts caused by replication mechanism (i.e.
    which write event "wins"?)

Before pursuing this further, I would be happy if you could share
experience (if any) or general estimates on this.

Thanks

Martin


-- 
Dr. Martin Haase, Solutions Engineer

DAASI International GmbH        
Europaplatz 3                   
D-72072 Tübingen                
Germany                    

phone: +49 7071 407109-0
fax:   +49 7071 407109-9  
email: martin.haase at daasi.de
web:   www.daasi.de

Sitz der Gesellschaft: Tübingen
Registergericht: Amtsgericht Stuttgart, HRB 382175
Geschäftsleitung: Peter Gietz


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2247 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://shibboleth.net/pipermail/users/attachments/20161124/1b8cca5c/attachment.p7s>