...
Cross Cutting Concerns are a little bit different. These should be invisible to the users, but very helpful to the developers. Any Bounded Context may depend on any mix of Cross Cutting Concerns. This part is ok to be a web of dependencies, they are often external projects/libaries we have selected for use all throughout Besu.
| Business Logic | Cross Cutting Concerns |
|---|
- Consensus
- Proof of Work
- External (or none?): Proof of Stake
- driven by Engine API
- Clique
- IBFT
- QBFT
- P2P
- ETH/66 and prior
- DevP2P
- Execution
- EVM
- Tracing
- Transaction Management
- Tessera integration
- MEV
- public and private transaction support
- Synchronizing
- Full sync
- Fast sync
- Snap sync
- Checkpoint sync
- Backwards sync
- Storage
- World State
- Forrest
- Bonsai
- Snapshot (RocksDB specific)
- Verkle
- Blockchain
- Key-Value specific implementations under each.
| - Cryptography
- Elliptic Curves
- Signatures
- Hashing
- native implementations
- Serialization
- RLP
- JSON
- GraphQL(ish. it's a lot broader than just serialization)
- APIs
- RPC
- HTTP
- Websockets
- GraphQL
- IPC
|
(under investigation)
- Inversion of Control
- Dagger
- Spring
- Observability
- Logging
- Metrics
- Debugging extras
- Configuration
- PicoCLI
- Genesis state vs. named networks
- Builds
- Static code analysis
- Use-case specific distributions
- test automation
- Unit
- Integration
- System
- Fuzz
|
Proof of Concept:
Introduce Dagger to implement a vertical slice of functionality. We need to find a feature that touches on a few cross-cutting concerns, but just one Bounded Context.
...