google-cloud VS mangos

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

I'm writing a client application that uses https://github.com/nanomsg/mangos to connect to a server using the PUB/SUB protocol. I'm not sure how to handle server or network interrupts on the client. The application is just a for loop waiting for a message to arrive and the call a go routine to handle that message. Does anybody know a good example how to deal with network or server failures in GO? Or should the application just panic and let the OS create a new instance of the application? The client application will run as a daemon so users can not interact with it.