docs:End-to-end evaluation

[dettanym]

private-zikade: topology_test.go: This allows us to instantiate DHT nodes in memory and as it is, we can use it to ensure that our LibP2P privacy code is executed correctly across a client and a server node. We could extend it to a tiny network of say 16 nodes (?)

End-to-end tests:

• Dennis and team route traffic from public IPFS gateways to Thunderdome to test new features. They run Thunderdome to run the full stack (LibP2P, Bitswap, versioned to test new features) on AWS and collect stats. As they say on their docs, Thunderdome allows testing the IPFS codebase against real traffic patterns, in contrast with Testground.

• Will pointed to IPFS testground earlier. It allows us to run the IPFS codebase too, but under simulated traffic conditions (latencies, bandwidths, jitter) as well as create networks of different sizes. This might be what @ssveitch had in mind. Note that Testground can be deployed on ripple, using Kubernetes & Minikube. (Miti has some experience doing this on Ripple.)

• Note that we'll need help to put things together: We'll need to find the repo that uses the non-private Zikade. For example, Kubo uses Zikade somehow. The Bitswap repo is here. We'll need to use "our version" instead.