How funktionalio/pillars works
Main Components Identification
The system should be represented with these core components:
a. Core Framework Components:
• API Server (ApiServer.scala)
• Admin Server (AdminServer.scala)
• Configuration Management (Config.scala)
• Observability System (Observability.scala)
• Logging System (Logging.scala)
• Metrics Collection (Metrics.scala)
• Tracing System (Traces.scala)
b. Database Components:
• Doobie Integration (db-doobie module)
• Skunk Integration (db-skunk module)
• Migration System (db-migration module)
c. Integration Components:
• HTTP Client (http-client module)
• Redis Integration (redis-rediculous module)
• RabbitMQ Integration (rabbitmq-fs2 module)
• Feature Flags System (flags module)
┌─────────────────────────────────────────────────────────────┐
• Pillars Framework │
• ┬─────────────────────┬─────────────────────┤
• Core Layer │ Integration Layer │ Database Layer │
• ┼─────────────────────┼─────────────────────┤
• API Server │ - HTTP Client │ - Doobie │
• Admin Server│ - Redis Client │ - Skunk │
• Config │ - RabbitMQ Client │ - Migrations │
• Logging │ - Feature Flags │ │
• Metrics │ │ │
• Traces │ │ │
• ┴─────────────────────┴─────────────────────┘
Following relationships:
Additional Elements
Supporting elements:
• Configuration flow paths
• Observability data paths
• External service connections
• Module dependencies
Notes
Technical notes for:
• Scala 3 specific features
• TypeLevel stack integration points
• Extension points for custom modules
• Configuration requirements
Remember to include version information and any relevant TypeLevel stack dependencies in supplementary documentation.