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

Portable Cloud Programming with Go Cloud

blog.golang.org

Post reply on HN
Print view View original

111–120 of 158 posts

Re: Portable Cloud Programming with Go Cloud

#111

Post by sethammons »

weberc2 wrote: post #82
bhamta wrote: post #63

I like how Google tries to masquerade their corporate goals behind the 'portability' banner. Google Cloud is in a distant third place behind AWS and Azure, so ofcourse they don't want developers to have tight coupling to their competitors. This portable cloud strategy is a mirage. I haven't seen anyone migrate providers easily (we tried in my last company). In reality, you have to break the cloud agnostic abstraction…

Reminds me of the situation with SQL vendor abstractions. SQL even has a standard and it’s still difficult to migrate any nontrivial application.

ORMs immediately popped into my mind.

Re: Portable Cloud Programming with Go Cloud

#113

Post by bschwindHN »

erik_seaberg wrote: post #80
paulddraper wrote: post #19

Earlier quoted context omitted.

You're correct. I was in no way surprised by this language feature, and neither were any of my coworkers. Go is a thoroughly "unsurprising" language.

A fatal error that prevents deployment is a lot more surprising than a warning.

You shouldn't even be at the point of attempting a deploy if your code doesn't compile.

Re: Portable Cloud Programming with Go Cloud

#114

Post by pinkgodzilla »

fishywang wrote: post #68
pinkgodzilla wrote: post #30

I wonder what kind of monitoring and alert system must exist if any cloud provider changes their SDK or APIs (signature, logic, capability etc.) upstream while your go binaries are in production. Did Google manage to get cloud providers on board to register and update a 1 to 1 match between the upstream api and the go cloud api? Secondly on the article's mention on multi cloud usage, you would need to be a pretty lar…

I don't think cloud providers would just change their SDK or APIs without notice. It will break anyone using their SDK, not only go-cloud. For your second point, it's normal for small startups to shop around and pick the cloud provider that's more suitable for their needs. For example on my last job at a small startup, we switched from AWS to GCP for cost reasons, and I implemented an abstraction (similar to go-cloud…

They never change over the course of say 3 years? 5 years? If it changes frequently that's great - someone could be put to task to monitor. If it changes very rarely, you will have a surprise outage although I am guessing debugging and fixing it would not be an issue unless you have SLAs you need to keep up with.

Re: Portable Cloud Programming with Go Cloud

#115

Post by pinkgodzilla »

outworlder wrote: post #71
pinkgodzilla wrote: post #30

I wonder what kind of monitoring and alert system must exist if any cloud provider changes their SDK or APIs (signature, logic, capability etc.) upstream while your go binaries are in production. Did Google manage to get cloud providers on board to register and update a 1 to 1 match between the upstream api and the go cloud api? Secondly on the article's mention on multi cloud usage, you would need to be a pretty lar…

> Secondly on the article's mention on multi cloud usage, you would need to be a pretty large place to need (or even bothering to assess and convince yourself that you need) to use multiple cloud providers at once. Oh, this is not the case at all. Do business with any retailer? Try telling them your stuff is hosted on AWS and see how that works for you.

If this occurred frequently for my business, you would architect your system for on-prem flexibility and capabilities. However, I think for just "data" like S3 blob storage, this is definitely a no brainer. I would imagine for VMs its going to be a lot more difficult with load balancing, permissions and what not.

Re: Portable Cloud Programming with Go Cloud

#116

Post by thermodynthrway »

cflewis wrote: post #27

Hey ho. I worked on this project. The majority of the team is in SF for Google Cloud Next to present this. I'm about to hop into the car to head up myself to watch, so I can do a little AMA throughout the day. Reply to this to make sure I see your question! Here's a question I've already seen: > Is this a Google project or a Go project? It is a project led by the Go team, and we are very aware of our responsibility t…

After Google threw half of Android into "Google Play Services" I don't believe it.

> Then anyone can code implementations to that interface for whatever cloud they like in separate repos, similar to the way `database/sql` is structured

Of course they can, but you're working on a Google-centric version first right? Otherwise why would it be at Google Cloud Next?

That makes all other cloud providers second tier, and I don't think you should call yourselves "platform neutral". If you were, you would code up multiple platforms from the beginning, like is normally done for support on different operating systems for example

Re: Portable Cloud Programming with Go Cloud

#117

Post by marcus_holmes »

cloverich wrote: post #100
untog wrote: post #67

Earlier quoted context omitted.

Go is certainly very easy to reckon with. But I was surprised at how little O cared for it when I tried it, given the hype I'd heard. The two things that immediately jumped out at me were error handling and generics. I understand both were deliberate choices but I'm still surprised they were made - I've been working with Swift a lot lately and it just feels like it makes so much more sense to me. I do love how opinio…

I feel like a caveman typing out error handling code in go, but on the other hand (even as a beginner in Go) I _never_ run into unexpected conditions. There's tradeoffs of course but every time I find myself thinking about what kinds of error conditions may be happening in my Node code (where I spend most of my time), and whether I covered them all... i think I'd trade.

this. I'm writing a system in Go and Vue at the moment, and while there is a certain tedium to writing "if err != nil { " for the thousandth time, I'm happy that if an error occurs somewhere it's not going to get silently passed up the stack until it pops up somewhere totally out of context.

Re: Portable Cloud Programming with Go Cloud

#118

Post by latchkey »

enjoylife wrote: post #58
skybrian wrote: post #51

Interesting that they built a new dependency injection framework, much like similar things in Java. I guess this doesn't replace Context, though? https://github.com/google/go-cloud/tree/master/wire

Doesn't replace context, and neither is it alone in terms of being a DI library, [1]. [1] https://github.com/uber-go/fx

As a Java engineer, I really missed DI in golang. Then I found fx.

Once I wrapped my brain around fx, I really liked it and used it heavily in a project I wrote. It was especially good for initializing 'things' of the same 'type'. Like a bunch of controllers for a web app.

One nice thing about fx is that it does not rely on code generation (uses reflection instead). I'm very curious what other features wire has over fx.

Post reply on HN