External HTTP calls and Endpoints

[David Sinclair]

Hi,

I am trying to use go-kit for my new micro-service and had a design question as far as how the go-kit way of doing it would be. There are existing HTTP APIs I need to reach out to and was curious if the recommended way of doing this with go-kit is to create a service interface, much like you would for creating an API to expose, along with new Endpoints and configure a transport. I think the real question I am still wrapping my head around is when to define and Endpoint vs just writing, what is IMHO, at times simpler code for some interaction. I realize a lot of the middleware is based on the Endpoint abstraction, but you could also do middleware based on the service as well. I have looked at the examples and have seen the profilesvc constructing endpoints for the client, so maybe I am answering my own question. 

Any guidance/best practices would be appreciated!

Thanks,

Dave