@@ -179,7 +179,7 @@ func encodeResponse(_ context.Context, w http.ResponseWriter, response interface
179179
180180## stringsvc1
181181
182- The complete service so far is [ stringsvc1] ( https://github.com/go-kit/kit /blob/master/examples /stringsvc1 ) .
182+ The complete service so far is [ stringsvc1] ( https://github.com/go-kit/examples /blob/master/stringsvc1 ) .
183183
184184```
185185$ go get github.com/go-kit/kit/examples/stringsvc1
@@ -200,7 +200,7 @@ No service can be considered production-ready without thorough logging and instr
200200## Separation of concerns
201201
202202Separating each layer of the call graph into individual files makes a go-kit project easier to read as you increase the number of service endpoints.
203- Our first example [ stringsvc1] ( https://github.com/go-kit/kit /blob/master/examples /stringsvc1 ) had all of these layers in a single main file.
203+ Our first example [ stringsvc1] ( https://github.com/go-kit/examples /blob/master/stringsvc1 ) had all of these layers in a single main file.
204204Before we add more complexity, let's separate our code into the following files and leave all remaining code in main.go
205205
206206Place your ** services** into a service.go file with the following functions and types.
@@ -475,7 +475,7 @@ func main() {
475475
476476## stringsvc2
477477
478- The complete service so far is [ stringsvc2] ( https://github.com/go-kit/kit /blob/master/examples /stringsvc2 ) .
478+ The complete service so far is [ stringsvc2] ( https://github.com/go-kit/examples /blob/master/stringsvc2 ) .
479479
480480```
481481$ go get github.com/go-kit/kit/examples/stringsvc2
@@ -661,7 +661,7 @@ func proxyingMiddleware(instances string, logger log.Logger) ServiceMiddleware {
661661
662662## stringsvc3
663663
664- The complete service so far is [ stringsvc3] ( https://github.com/go-kit/kit /blob/master/examples /stringsvc3 ) .
664+ The complete service so far is [ stringsvc3] ( https://github.com/go-kit/examples /blob/master/stringsvc3 ) .
665665
666666```
667667$ go get github.com/go-kit/kit/examples/stringsvc3
@@ -728,6 +728,6 @@ It's possible to use Go kit to create a client package to your service,
728728 to make consuming your service easier from other Go programs.
729729Effectively, your client package will provide an implementation of your service interface,
730730 which invokes a remote service instance using a specific transport.
731- See [ addsvc/cmd/addcli] ( https://github.com/go-kit/kit /blob/master/examples /addsvc/cmd/addcli )
732- or [ package profilesvc/client] ( https://github.com/go-kit/kit /blob/master/examples /profilesvc/client )
731+ See [ addsvc/cmd/addcli] ( https://github.com/go-kit/examples /blob/master/addsvc/cmd/addcli )
732+ or [ package profilesvc/client] ( https://github.com/go-kit/examples /blob/master/profilesvc/client )
733733 for examples.
0 commit comments