Thanks for the suggestion. I'd previously added the tutorial linked below, but that clearly wasn't cutting it, so I've now added an example diagram for first-time visitors. If you already visited, click on the top object (probably the help text), press shift-D to delete all items, then refresh the page.
I spend lots of my time at a whiteboard diagramming current or proposed systems. The whiteboard experience is less than ideal: my handwriting isn't great, folks on the other side of a VC can't see, etc. Most diagramming software is designed for careful human placement to get precise results. I built Architype to let me take notes and play with system designs in real time during a conversation, in a way that can be easily projected. It's designed to be entirely client-side and fast, but still powerful enough to produce useful diagrams for most purposes.
In the linked example for the tutorial, I see there is a "gRPC" label for the links inside the two region groups, however, I am not seeing that label show up anywhere on the diagram. Is that expected behavior?
Other than that, very promising project and the vi keybindings are a nice touch.
This is a networking issue, and your data is safe. Cloud SQL stores instance metadata regionally, so it shares a failure domain with the data it describes. When the region is down or inaccessible, instances are missing from the list results, but that doesn't say anything about the instance availability from within region.
That's good to know. What confuses me is why they're saying "We continue to experience high levels of network congestion in the eastern USA", when I'm in us-west2 (Los Angeles) and none of my CloudSQL instances, nor is my k8s cluster showing up or contactable...
This is a networking issue, and your data is safe. Cloud SQL stores instance metadata regionally, so it shares a failure domain with the data it describes. When the region is down or inaccessible, instances are missing from the list results, but that doesn't say anything about the instance availability from within region.
[I'm the Cloud SQL TL] I can't comment on timelines, but we're aware that customers are interested in more features around maintenance window scheduling, deferral, and notification, as well as shorter downtime for updates and smarter scheduling within a group of replicas.
[I'm the Cloud SQL TL] Confirmed. We know it's a problem that we need to fix. HA reduces downtime in unexpected failure cases (live migration for your primary only helps in planned shutdown cases, not if the physical machine fails), but doesn't currently help with maintenance-related downtime.
[I'm the Cloud SQL TL] Note that we currently only support PostgreSQL 9.6. Obviously supporting major versions across both MySQL and PostgreSQL is a priority for us.
[I'm the Cloud SQL TL]
No, it isn't. We agree with you that it's an important feature for managed databases, and we're working to get it right. We decoupled it from this launch to get PostgreSQL to GA faster.
Unrelated to pg but could you badger the spanner team to make a mini spanner product :)
Related to postgres. We have many many concurrent connections but a load satisfied by an n1-standard-4 atm do you recommend a connection pooler or something to help us get down to the 100 to 200 connections we need to be at to use cloudsql?
