I am running a webapp from a uk datacenter. Speed is fine as expected. The webapp relies heavily on a database. I would like to open the webapp to Australia and New Zealand but maintain good response time from the server.
Essentially the each user in the app has access to data stored in two tables in the db. Each user uses said data to generate their own combination of this data and store in other tables in the db. There are few asset updates to the app.
Registered emails would need to be unique in all countries.
From my limited knowledge in this area I believe there are two options: A - Full database replication between two hosts, one in the UK and one in AUS B - Periodic replication of data from a source host, the uk, to the targets, in aus and nz.
This then leaves the domain 1 - Ideally on domain would be best however this would need a routing server of sorts to direct traffic based on location to different servers, but this would increase response time 2 - Have alternate domains per country routing directly to the country local host
I appreciate I am not reinventing the wheel here but what is the std protocol for a scenario like this? A cdn service from my understanding here is more for image and video delivery, i suppose the base question here is what is the equivalent for databases?
Thanks for any help, John