Current orderer implementation is
- Tightly coupled with reading config from local files
- Using
cryptogen
before setting up orderer is unnecessary, however current impl forces one to do that - Not well documented
- Tied to docker-compose
- Bootstrapping orderer is complicated and requires co-ordinating files
This implementation reuses most parts of the existing orderer, but
- cleans up the design
- is loosely coupled and modular
- is not tied to docker-compose
- meant to run on Kubernetes
- meant to aid dynamic addition of new orgs (orderers, peers, msps)
and Docs! expect a lot of Docs!