ARCHITECTURE: set of ADRs of the project.

[matiwinnetou]

Retrospectively document architecture decisions of the project via a set of ADRs (Architecture Definition Records).

ADRs backlog:

• why there is a ledger follower and it's function. Why is it a read-only service
• why was Yaci-Store chosen instead of using blockfrost / koios only
• why JWT <> WEB3 auth bridge
• why microservice architecture instead of a e.g. modularised monolith
• why vote-commitment-service is a service instead of being a standalone job run by some scheduler
• why vote-commitment is not part of a voting-app and has been separated out
• why is vote-commitment service sharing db with a voting app without using any messaging system in between (e.g. kafka)
• why there is no generic UI app to host events but UI apps are always event specific
• what was CIP-93 used for
• why CIP-30 signatures use JSON in the frontend instead of CBOR serialisation
• why has Hydra been used to tally the votes and pros and cons of this
• Explain on chain event and category registration transaction formats
• Document schema evolution from V1 to V11 (1.1.0) (maybe even CIP?)