mysql - Single Cloud SQL or multiple databases? -



mysql - Single Cloud SQL or multiple databases? -

not sure how inquire question, understand google cloud sql supports thought of instances, located throughout global infrastructure...so can have single database spread across multiple instances on world.

i have a few geographic regions our app serves...the info doesn't need aggregated whole , stored individually on separate databases in regions accordingly.

does create sense serve regions off 1 database/multiple instances? or should segregate each part it's own database , host info old fashion way?

if “scaling” mean memory size, can start smaller instance (less ram) , move more powerful instance (more ram) later.

but if mean more operations per second, there max size , max number of operations 1 cloud sql instance can support. cannot infinitely scale 1 instance. internally info 1 instance indeed stored on multiples machines, more related reliability , durability, , not scale throughput beyond limit.

if need more throughput 1 cloud sql instance can provide, , need sql based storage, you’ll have utilize multiple instances (i.e. separate databases) app have manage them.

note advantages of cloud go beyond scalability. cloud sql instances managed (e.g. failover, backups, etc. taken care of). , billing based on usage.

(cloud sql team)

mysql google-cloud-sql

Comments

Popular posts from this blog

formatting - SAS SQL Datepart function returning odd values -

c++ - Apple Mach-O Linker Error(Duplicate Symbols For Architecture armv7) -

php - Yii 2: Unable to find a class into the extension 'yii2-admin' -