Please share with the community what you think needs improvement with Google Cloud SQL.
What are its weaknesses? What would you like to see changed in a future version?
In my humble opinion, nothing can be improved. It's a good solution as it is. What could be refined however is the ability to have more than just one secondary/replication site. At the moment you can have a primary DB and a replica one, but having the option to add a third or fourth replication site would be fantastic.
The only room for improvement here is that they need to connect to more existing data sources so that it becomes easier for a layman to get a more realistic understanding of what's happening. They don't put data outside of the cloud storage. If I can query and there is some way for me to ingest it with various query cells, that would be great. Better connectivity with other marketing tools would be helpful. Right now it's limited in scope relative to the other connectors. So they should build more connectors, making it easier to connect the data. There's no standalone application that I could just click and start shooting it.
Better integration with other tools could improve this solution. For example, data analytics is very important, so that's why I go to BigQuery. They should make things more user-friendly, not technically on the use of SQL but when it comes to integrating it with other tools, it could be like dashboards or business intelligence. I believe Google is already working on that as well because they bought Looker about a month ago. I would like to see better integration with all the different tools on the platform.
In my opinion the most vulnerable problem with Google SQL is each SQL node is provided with a public IP address. They provide you the option or ability to customize your access control list, but at the end of the day, it's a public IP address.