guanw / ct-dns Goto Github PK

https://rakyll.org/grpc-streaming/

https://github.com/grpc/grpc-go/blob/master/examples/route_guide/server/server.go
https://github.com/grpc/grpc-go/blob/master/examples/route_guide/client/client.go

1. https://github.com/gomodule/redigo
2. https://github.com/mediocregopher/radix

https://markheath.net/post/exploring-redis-with-docker

candidate:

1. zap
2. zerolog
3. logrus

https://semaphoreci.com/community/tutorials/how-to-perform-integration-testing-on-go-applications-with-docker
specify // +build integration in xxx_test.go file
and use go test -tags integration to run integration

https://www.philosophicalhacker.com/post/integration-tests-in-go/

https://stackoverflow.com/questions/25965584/separating-unit-tests-and-integration-tests-in-go/25970712

this is kind of blocked by #36 .

heartbeat -> (optional: kafka ->) api server -> redis ttl record

idea 1: health check agent on individual host of running service.

idea 2: service constantly reports themselves to ct-dns backend and set ttl.

idea 3: separate service doing health check after scanning all available services.

On startup, new service host should be able to register their host/port/etc information with ct-dns. Brainstorm the best way to do it.

support reading config from yml, make it as priority compared to passing via command flags?

try to evaluate current handlers

reference: https://gist.github.com/kelvinn/6a1c51b8976acf25bd78

optional: add rate limit

https://prometheus.io/docs/guides/go-application/

To start:

implement /v2/discovery:endpoints and /v1/registration/{serviceName} (done by #50 and #51 )

https://medium.com/@salmaan.rashid/envoy-control-plane-hello-world-2f49b2865f29

TODO 1

next: use go-control-plane to implement v2

https://www.lijiaocn.com/%E9%A1%B9%E7%9B%AE/2018/12/29/envoy-07-features-2-dynamic-discovery.html#%E5%AE%89%E8%A3%85go-control-plane

1. try to implement a minimum working server.Server with gateway at front first for current envoy.yaml to work.
2. update envoy.yaml to make eds query working with grpc instead of http.

Update: (This might not be needed as I only intend to provide EDS implementation as an example)
Also see this

TODO 2

support specifying multiple services dynamically?

right now the schema only gives host and port. Need to support protocol as well.

1. environment variable

viper https://github.com/spf13/viper

initially I want record to expire with a ttl because we might have a separate service that does healthcheck polling and remove any invalid hosts.

etcd: https://godoc.org/github.com/coreos/etcd/clientv3#example-Lease--Grant

1. It's good for starting out
2. It's good for testing concurrency

Scenario: if the write/get from store fails, it might be due to random reason like instable network.
Should add protection mechanism for retry to minimize this type of impact.

references:

https://www.bogotobogo.com/GoLang/GoLang_Web_Building_Docker_Image_and_Deploy_to_Kubernetes.php

https://medium.com/@yusufkaratoprak/a-simple-golang-application-via-kubernetes-8a200235a45a

https://www.callicoder.com/deploy-multi-container-go-redis-app-kubernetes/

1. schema for dynamodb
2. setup for etcd/redis/dynamodb etc
3. how to run ct-dns in docker container
4. how to run ct-dns with redis in kubernetes