Files
proxmox/docs/archive/00-meta-pruned/SERVICE_DEPENDENCY_GRAPH_PLAN.md
defiQUG fbda1b4beb
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
docs: Ledger Live integration, contract deploy learnings, NEXT_STEPS updates
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands
- CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround
- CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check
- NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere
- MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates
- LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-02-12 15:46:57 -08:00

1.4 KiB

Service Dependency Graph Plan

Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation


Date: 2026-01-22
Status: 🟢 Planning
Purpose: Create visual service dependency graph


Summary

  • Services: 80+ containers across multiple categories
  • Dependencies: Database, Redis, API, Network, etc.
  • Status: Need to map all dependencies

Dependency Categories

Database Dependencies

  • PostgreSQL (Order, DBIS, Sankofa)
  • Redis (Order, DBIS, RPC Translator)

API Dependencies

  • DBIS API → PostgreSQL, Redis
  • Order API → PostgreSQL, Redis
  • Sankofa API → PostgreSQL, Keycloak

Network Dependencies

  • NPMplus → Backend services
  • Cloudflare Tunnel → NPMplus
  • Nginx → Application services

Blockchain Dependencies

  • RPC Nodes → Besu Validators
  • Blockscout → RPC Nodes
  • Bridge Services → RPC Nodes

Implementation Plan

Phase 1: Map Dependencies

  1. Document all service dependencies
  2. Identify dependency types
  3. Map dependency relationships

Phase 2: Create Visual Graph

  1. Use Mermaid or similar tool
  2. Create dependency diagram
  3. Include dependency types

Phase 3: Document

  1. Create dependency documentation
  2. Document startup order
  3. Document dependency resolution

Last Updated: 2026-01-22
Status: Planning complete, ready for implementation