It seems this service is targeted towards specific applications where write traffic is somewhat independent between 2 regions. However, you can shoot yourself in foot, if 2 regions are trying to update the same row, because of eventual consistency.
>> You can now create tables that are automatically replicated across two or more AWS Regions, with full support for multi-master writes, with a couple of clicks. <<
Hamm, If I understand it correctly, REGIONS are no longer heavily isolated.
I would say this offers global capabilities while preserving regional isolation. you're composing the global table out of regional tables (which replicate between each other), and you're still using regional endpoints. this means that a failure with one region's table does not have impact on the other.
this model does mean that certain things, like conditional expressions, are less useful/useless because you could very well execute a conditional expression against stale date.
johnvega|8 years ago
sheraz|8 years ago
Not sure from a quick peek if DynamoDB does the same...
uji|8 years ago
ramshanker|8 years ago
Hamm, If I understand it correctly, REGIONS are no longer heavily isolated.
seniorsassycat|8 years ago
Global tables use DynamoDB Streams put items from Table A to Table B using conditional put (A Timestamp > B Timestamp).
Automated backup may be DynamoDB Streams or an automated setup of Datapipelines export to s3.
http://docs.aws.amazon.com/datapipeline/latest/DeveloperGuid...
dastbe|8 years ago
this model does mean that certain things, like conditional expressions, are less useful/useless because you could very well execute a conditional expression against stale date.