google-cloud VS go-cloud

Hello. So we use big query as database for all events that are happening in the project. And one of the features on the frontend is to display events with detailed view and so. Also one thing that we're using there is infinite scroll, so you can hit and fetch more requests. Based on that I do not know if the current approach is something correct. Basically we need out of process pagination where we create a job on the first request and then on next requests we paginate over the results. Using more or less this solution now: https://github.com/googleapis/google-cloud-go/issues/8173

I am trying to run the tests with https://github.com/googleapis/google-cloud-go.

is this different from google’s? https://github.com/googleapis/google-cloud-go/wiki/Iterator-Guidelines

Go

I would go with GCP. There are Go examples everywhere in the GCP documentation and here is the official Go lib for GCP https://github.com/googleapis/google-cloud-go

I'm struggling to find the idiomatic Go SDK API from GCP and how to use the existing one https://cloud.google.com/go/docs/reference # don't have DNS package https://github.com/googleapis/google-cloud-go # don't have DNS package https://github.com/googleapis/google-api-go-client # has DNS package but I can't find one way to list my managed DNS zones So in this case, what can I do? So far I've done the following, I want to change the func hostList() to something dynamic generated based on my Google Cloud DNS zones.

package logx import ( "fmt" "net/http" ) func info(r *http.Request, message interface{}, projectID string) { get := r.Header.Get("X-Cloud-Trace-Context") traceID, spanID, traceSampled := deconstructXCloudTraceContext(get) traceID = fmt.Sprintf("projects/%s/traces/%s", projectID, traceID) entry := logEntry{ Severity: "INFO", Message: message, HttpRequest: &httpRequest{ RequestMethod: r.Method, RequestUrl: r.URL.String(), UserAgent: r.UserAgent(), RemoteIp: r.RemoteAddr, Referer: r.Referer(), }, Timestamp: time.Now(), Labels: map[string]string{"labels": "rock"}, SpanID: spanID, TraceID: traceID, TraceSampled: traceSampled, } writelog(&entry) } func writelog(entry *logEntry) { if err := json.NewEncoder(os.Stderr).Encode(entry); err != nil { fmt.Printf("failure to write structured log entry: %v", err) } } // taken from https://github.com/googleapis/google-cloud-go/blob/master/logging/logging.go#L774 var reCloudTraceContext = regexp.MustCompile( // Matches on "TRACE_ID" `([a-f\d]+)?` + // Matches on "/SPAN_ID" `(?:/([a-f\d]+))?` + // Matches on ";0=TRACE_TRUE" `(?:;o=(\d))?`) func deconstructXCloudTraceContext(s string) (traceID, spanID string, traceSampled bool) { // As per the format described at https://cloud.google.com/trace/docs/setup#force-trace // "X-Cloud-Trace-Context: TRACE_ID/SPAN_ID;o=TRACE_TRUE" // for example: // "X-Cloud-Trace-Context: 105445aa7843bc8bf206b120001000/1;o=1" // // We expect: // * traceID (optional): "105445aa7843bc8bf206b120001000" // * spanID (optional): "1" // * traceSampled (optional): true matches := reCloudTraceContext.FindStringSubmatch(s) traceID, spanID, traceSampled = matches[1], matches[2], matches[3] == "1" if spanID == "0" { spanID = "" } return }

The Google Cloud Client Libraries for Go generally use gRPC under the hood to connect with Google Cloud APIs. When you create an API client, the library initializes a connection to the API then leaves that connection open until you call Close on the Client.

Anyone have experience with testing google pubsub event handlers locally? https://github.com/googleapis/google-cloud-go/tree/pubsub/v1.5.0/pubsub

Even when going multi-cloud you can employ different strategies. Vault is definitely one of them, but you can also use federation to exchange one cloud's credentials for another's, giving you the ability to centralize secrets in one of them. You can use a layer of abstraction like GoCloud [0]. You can also build for each cloud separately and decide either not to centralize secrets at all, or build some trivial bespoke tooling to synchronize some of them. I'm not endorsing any of the options, just pointing out that Vault isn't the only one.

https://github.com/google/go-cloud

> If Google started adding Google Cloud specific primitives natively to Go would you call that forward thinking as well?

Go actually ships with a quite forward thinking SQL interface. It's an abstract interface over a DB, and you just import the "driver" that powers it. The driver conforms to a standard interface, so all of them behave roughly the same.

I think this is what everyone wants from Deno/etc - why can't there also be a KV interface that's universal, or a Queue interface that's universal?

People attempted this w/ go [1], where it attempts to use the same nice experience of the SQL logic, but it never seemed to gain traction.

https://gocloud.dev

github.com/google/go-cloud/pubsub package provides a set of interfaces and tools to work with publish/subscribe messaging. This package allows easy communication between independent components by decoupling the sender and the receiver.

I'm guessing this is a reasonable example of what they're using it for? server.go

https://github.com/google/go-cloud probably out of context, but not IaC but agnostic backend development with Go across multiple clouds

The plan is to have a process for generating AWS CDK targeting Lambda (pluggable providers, but start with AWS CDK, because it's what I use), and to use the Google Cloud Development Kit (also called CDK, but not the same) https://github.com/google/go-cloud to abstract the services.

In this post, I will talk about an exciting project maintained by the team that develops the Go language: the Go Cloud Development Kit, also known as the Go CDK.

The API of gocloud.dev, is stable. We are at ariga.io, already use gocloud.dev for internal service, and even in the public for easy adopt multi-clouds provider: https://github.com/ariga/atlas/commit/ef0b0eae65a61375482497ceb9ed9790a469b56e

On Go, which has a community focused on the cloud, there is even GoCloud, a library with a single, common, and high-level API that allows an application to support any of those clouds and even on-premise alternatives for those services. All can be configurable at deploy time by the infrastructure team.