Daniel Caballero

https://github.com/golang-standards/project-layout

That is the most external layer with the actual tcpgoon core functionality: we will introduce several scenarios

First service discovery integration to pick one instance/IP - Eureka

5

In order to facilitate the consumption for services not statially tied to a single DNS (or maybe behind a load balancer we don't want to test), discovering and testing an...

I started to cover this: https://github.com/dachad/tcpgoon/issues/36 And following a tdd approach... tests are quite complete (but end to end), and main pending points are: * complete eureka client implementation passing...

In one hand, we have a tcpconnect function that supports a waitgroup to report how many connections have been processed, so they can be called inside goroutines and allow the...

... so we can provide some expectations in the README about max tcp connections we can test in a single instance