Page History

...

Remaining data is expected to be per-Region(including Projectsprojects, global config, resource limits) and not shared across databases in other Regions. 

...

• When creating the account, it is created first in the Region that the user is logged into
• Account table will include region_id column, indicating the Region that it is created from
• This Region is responsible for propagation of Account creation to other Regions
• Account deletion/modification is always forwarded to the Region that originally created the account 
• The Region that originally created account is responsible for deleting the account from all of the regions before it declares the account is deleted. If it cannot reach an Region, an entry is created in the region_sync table with api details.

...

Update/Remove: Request is forwarded to the source region. After updating the resource locally, source region sends API requests to peer regions with ispropogate flag set to true.

If any sync API call made by source region fails,an entry will be added to region_sync table with API details. The operation itself won't fail provided the changes were successfully applied locally.

Authentication

Once logged in User should be able to switch from one Region to another without providing credentials again

...