Similar to travis-ci/gimme
, except a little more robust. Designed for Travis servers.
There are several schemes:
package main | |
import ( | |
"fmt" | |
"io" | |
"log" | |
"net/http" | |
"os" | |
"time" | |
) |
package main | |
import ( | |
"context" | |
"fmt" | |
"io" | |
"log" | |
"net/http" | |
"os" | |
"os/signal" |
package main | |
import ( | |
"flag" | |
"fmt" | |
"io/ioutil" | |
"path" | |
"path/filepath" | |
"strings" | |
"sync" |
FROM alpine | |
RUN apk add --update ca-certificates | |
COPY app /app | |
ENTRYPOINT /app |
FROM alpine | |
RUN apk add --update ca-certificates | |
COPY app /app | |
ENTRYPOINT /app |
runtime: go | |
api_version: go1 | |
handlers: | |
- url: /.* | |
script: _go_app |
You know that latency matters. Lower latency correlates to an increase in user engagement, sales and user satisfaction. In this session, we'll talk about sources of latency, how to investigate it (including benchmarking, profiling and tracing), how to minimize it and how to approach application design and make architectural decisions with latency in mind.
Video: https://www.youtube.com/watch?v=G8KuiDimU9w
Slides: Link TBD
package main | |
import ( | |
"fmt" | |
"net/http" | |
"strings" | |
"github.com/davecgh/go-spew/spew" | |
oauth2 "google.golang.org/api/oauth2/v2" |
package main | |
import ( | |
"bytes" | |
"encoding/json" | |
"flag" | |
"fmt" | |
"io" | |
"io/ioutil" | |
"log" |