P2P Networking

**Break into smaller work units**

https://github.com/coast-team/netflux

While microservices operate primarily stateless, under scaling events and an event driven system a centralized communication / que / work tracker of which copy of this service is working on which item in the stream is important.

Maintaining such information allows for recovery of failed state / crashes logic to be enabled in code without a full transaction verification system via poll of clients.

This approach also fits well with the TAP method in Functional Programming Libraries.

NOTE: [Zyre](https://github.com/interpretor/zyre.js/) could have been used as an alternative but the broadcast nature of it is blocked in most cloud providers and CNI providers with Kubernetes

connects #21

Start by reading the linked netflux project and issue #21 to understand the proposed peer-to-peer coordination approach. Break the broad P2P Networking proposal into smaller work units, with completion defined by an agreed design for tracking work across service copies and recovering after failures.

Written by the indexing model from the issue text.