Update addsvc

circle.yml

@@ -17,7 +17,7 @@ test:
     - mkdir -p /home/ubuntu/.go_workspace/src/github.com/go-kit
     - mv /home/ubuntu/kit /home/ubuntu/.go_workspace/src/github.com/go-kit
     - ln -s /home/ubuntu/.go_workspace/src/github.com/go-kit/kit /home/ubuntu/kit
-    - go get github.com/go-kit/kit/...
+    - go get -t github.com/go-kit/kit/...
   override:
     - go test -v -race -tags integration github.com/go-kit/kit/...:
         environment:

examples/addsvc/README.md

@@ -0,0 +1,17 @@
+# addsvc
+
+addsvc is an example microservice which takes full advantage of most of Go
+kit's features, including both service- and transport-level middlewares,
+speaking multiple transports simultaneously, distributed tracing, and rich
+error definitions. The server binary is available in cmd/addsvc. The client
+binary is available in cmd/addcli.
+
+Finally, the addtransport package provides both server and clients for each
+supported transport. The client structs bake-in certain middlewares, in order to
+demonstrate the _client library pattern_. But beware: client libraries are
+generally a bad idea, because they easily lead to the
+ [distributed monolith antipattern](https://www.microservices.com/talks/dont-build-a-distributed-monolith/).
+If you don't _know_ you need to use one in your organization, it's probably best
+avoided: prefer moving that logic to consumers, and relying on 
+ [contract testing](https://docs.pact.io/best_practices/contract_tests_not_functional_tests.html)
+to detect incompatibilities.