Changes

Identity/AttachedServices/StorageServiceArchitecture

253 bytes removed, 05:13, 11 June 2013

→‎Summary

* The client-facing API is strongly consistent, and exposes an atomic check-and-set operation.

** This makes an eventually-consistent NoSQL store rather less attractive, unless coupled with a strongly-consistent control layer e.g. zookeeper.

* Initial deployment will be into AWS.

** Assuming PiCL succeeds in replacing sync, we can probably subsume some of the sync hardware over time.

* It's OK to have brief periods of unavailability

Confirm

358

edits