Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google Cloud Platform’s new interactive CLI

cloudplatform.googleblog.com

Post reply on HN
Print view View original

61–70 of 79 posts

Re: Google Cloud Platform’s new interactive CLI

#61

Post by rdsubhas »

optimusclimb wrote: post #28

I wish they would spend more time finishing the halfway done projects they've started (and fully documenting them), rather than continue to launch new ones. For instance...Google CloudSQL - Great! Postgres - Beta...Postgres from AppEngine python...err, we'll get around to it, maybe. Just giving one example, but my point is - finish what you've started before making new. I think recent articles I've read about launchi…

It's repeated enough that it's a conscious decision. Google offers good application platform, but locks in the data layer.

See AppEngine. Had (and still has) much bigger potential than heroku since the beginning. But where do you store data? Random stores with random limits.

CloudSQL is great? Backup/restore in CloudSQL is half baked. Multi master for MySQL is half baked. All these are very well solved with RDS, but Google wants to sell you 3 or 4 different data stores with different arbitrary limits.

AWS free tier provides a tiny RDS insurance for you to store useful data. Google cloud free tier? No standard SQL databases. Again, arbitrary locked in custom nosql with random functionality and usage limits.

It's spread out enough that it looks like a planned strategy to give an open computation platform but lock in the data, even at the risk of driving away potential new/small customers.

Re: Google Cloud Platform’s new interactive CLI

#62

Post by laixer »

wetha wrote: post #58
manigandham wrote: post #55

Earlier quoted context omitted.

That is an understandably automatic control feature to keep the DB instance running well since PostgreSQL doesn't handle connection scaling well. The recommendation is to use pgbouncer, which you can also combine with the GCP cloudsql proxy into a separate container and use that way. We deploy that onto GKE as a service and have our apps use that. Some setup required but cleaner overall.

I assume CloudSQL is google’s alternative to AWS RDS. Less of an excuse to not make the setting user configurable when the competition (AWS) does.

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

Re: Google Cloud Platform’s new interactive CLI

#63

Post by bjd145 »

colemickens wrote: post #45
algorithmsRcool wrote: post #19

Earlier quoted context omitted.

Azure has one too https://docs.microsoft.com/en-us/azure/cloud-shell/overview

An interactive CLI (this) is not the really at all the same thing as a JavaScript TTY connected to a container (Cloud Shell). (Though, Google does also have a Cloud Console that is comparable to Azure's Cloud Shell.)

Cloud Shell has an interactive mode - https://docs.microsoft.com/en-us/cli/azure/interactive-azure...

Re: Google Cloud Platform’s new interactive CLI

#64

Post by shaunparker »

optimusclimb wrote: post #28

I wish they would spend more time finishing the halfway done projects they've started (and fully documenting them), rather than continue to launch new ones. For instance...Google CloudSQL - Great! Postgres - Beta...Postgres from AppEngine python...err, we'll get around to it, maybe. Just giving one example, but my point is - finish what you've started before making new. I think recent articles I've read about launchi…

I've been waiting for Cloud Postgres as well and wish I could have used it on my most recent project. I was told last month by a "Cloud Specialist" that they were targeting early Q2 of this year to leave beta, but I'll believe it when I see it.

I also find it frustrating that they don't have more turnkey services. In particular, search. It's ironic that Google's doesn't offer a search service (except if you use App Engine).

Re: Google Cloud Platform’s new interactive CLI

#65

Post by antisocial »

optimusclimb wrote: post #28

I wish they would spend more time finishing the halfway done projects they've started (and fully documenting them), rather than continue to launch new ones. For instance...Google CloudSQL - Great! Postgres - Beta...Postgres from AppEngine python...err, we'll get around to it, maybe. Just giving one example, but my point is - finish what you've started before making new. I think recent articles I've read about launchi…

I have 300$ of trial credit, but couldn't use it when I wanted to create Cloud Datalab notebooks for an ML MOOC under the pressure of deadlines. I was willing to spend more money on something that is working (Floydhub) than use these GCP credits and figure out how to use it.

Re: Google Cloud Platform’s new interactive CLI

#66

Post by bitmapbrother »

optimusclimb wrote: post #28

I wish they would spend more time finishing the halfway done projects they've started (and fully documenting them), rather than continue to launch new ones. For instance...Google CloudSQL - Great! Postgres - Beta...Postgres from AppEngine python...err, we'll get around to it, maybe. Just giving one example, but my point is - finish what you've started before making new. I think recent articles I've read about launchi…

>I wish they would spend more time finishing the halfway done projects they've started

Do you expect other teams to halt what they're doing and wait for other teams to finish before they continue their work?

Re: Google Cloud Platform’s new interactive CLI

#67

Post by optimusclimb »

bitmapbrother wrote: post #66
optimusclimb wrote: post #28

I wish they would spend more time finishing the halfway done projects they've started (and fully documenting them), rather than continue to launch new ones. For instance...Google CloudSQL - Great! Postgres - Beta...Postgres from AppEngine python...err, we'll get around to it, maybe. Just giving one example, but my point is - finish what you've started before making new. I think recent articles I've read about launchi…

>I wish they would spend more time finishing the halfway done projects they've started Do you expect other teams to halt what they're doing and wait for other teams to finish before they continue their work?

No - I wish they'd release fully baked features before starting new ones - i.e. there'd be nothing to halt. I realize it's not that simple, but, generally speaking - I do not see near the level of readiness/polish/documentation out of existing features as exists on AWS.

Re: Google Cloud Platform’s new interactive CLI

#68

Post by shankun »

optimusclimb wrote: post #28

I wish they would spend more time finishing the halfway done projects they've started (and fully documenting them), rather than continue to launch new ones. For instance...Google CloudSQL - Great! Postgres - Beta...Postgres from AppEngine python...err, we'll get around to it, maybe. Just giving one example, but my point is - finish what you've started before making new. I think recent articles I've read about launchi…

Hi all, the Google Cloud SDK team here. The Interactive CLI feature is currently in Alpha, but part of our overall Cloud SDK. The SDK is very much in GA, but we continue to look for your feedback on what we can do to make the SDK experience better and easier to use. If you’ve got feedback, we have a built-in mechanism in the SDK. Just enter ‘gcloud feedback’, and let us know.

Re: Google Cloud Platform’s new interactive CLI

#69

Post by shankun »

jmeyer2k wrote: post #15

AWS also has something similar called AWS Shell: https://github.com/awslabs/aws-shell

With the interactive CLI, we set out with a similar mission as other cloud CLIs - our first priority was helping users use the GCP CLIs including gcloud and gsutil. With our Interactive CLI, we’ve tried to build something that doesn’t just help new users discover what they can do, but also helps make more advanced users productive, for scenarios such as piping between commands, and shell redirection for read-edit-write workflows. The Interactive CLI provides a full shell environment, and isn’t restricted exclusively to the use of GCP tools.

Interactive CLIs like are a little different than a "cloud shell", which provides a fully cloud-hosted CLI environment. If you want a fully curated cloud-hosted option, check out https://cloud.google.com/shell/. Note that the Cloud Shell includes the Cloud SDK.

Post reply on HN