mysql - Single Cloud SQL or multiple databases? -


How to definitely ask this question, but as I think Google Cloud SQL supports the idea of ​​examples , Which is the entire global infrastructure ... so I can spread a single database across the world in many instances.

My APs are in some geographic areas ... Data is not really needed to fully collect and accordingly it can be stored separately on separate databases in areas.

Is it understandable to serve all the fields with a database / multiple instances? Or should I separate each area into my database and host the data in the old fashioned way? If "scaling" by you means memory size, then you get a small example (low RAM)

But if you have more operation per second, the maximum number of which can support a certain maximum size and a cloud SQL example. You can not raise an example infinitely Internally for an example, the data is actually stored on the majority of machines, but it relates more to reliability and stability, and does not scale throughput over a certain threshold.

If you really want more throughput, you can provide a SQL SQL example, and you need a SQL based storage, you will have to use several instances (i.e. completely different databases) , But your app must manage them.

Note that the benefits go beyond the scalability of the cloud Cloud SQL examples are managed for you (e.g., failure, backup, etc. are taken care of) and you get billing based on usage .

(Cloud SQL Team)


Comments

Popular posts from this blog

java - Can't add JTree to JPanel of a JInternalFrame -

javascript - data.match(var) not working it seems -

javascript - How can I pause a jQuery .each() loop, while waiting for user input? -