laixer

The limit was never 5. It used to be 12 and now it's 60.

Private IP support for Cloud SQL is on the roadmap. The reality of development is that some things are easier to do on a new product. It's not a matter of communication.

It's a double edged sword. When you don't limit connections and customers push their servers beyond their limits, some of them then ask why Google didn't do anything to prevent the situation from happening. Ideally, this would be solved by having better failure modes but that's not really the case today.

Most product decisions are not set in stone and can be changed if there's sufficient evidence to suggest that they do more harm than good. There's a lot of work that goes on behind the scenes to keep the service running smoothly and unfortunately/fortunately customers are not exposed to them. Some things that may appear to be simple on the surface are not when you take things like supportability into consideration.

Source: Used to work on Cloud SQL

It's a product decision to not make this configurable to make the service supportable. It's not a technical issue.

Looks pretty good (coming from a Anki user).

One piece of feedback: The toolbar UX in the deck is confusing as it's inconsistent with every other iOS app. The 'back' button should be on the left and the 'options' button needs to be on the right.

It will be available for all users early next week.

10TB.

No, it was mentioned in the keynote.

Cloud SQL for Postgres is launching today and will be available for all users early next week.

Source: Work on Cloud SQL.