How availproject/turbo-da works
Project type and purpose
• This is a full-stack, microservice-based Data Availability service (“TurboDA”) for the Avail DA chain.
• It exposes a Next.js dashboard (frontend) and a Rust-based REST API core service plus several background workers (data submission, funds monitor, fallback monitor).
• It integrates with PostgreSQL, Redis, multiple blockchain RPC endpoints (Avail, Ethereum, Base), plus external third-party APIs (CoinGecko).
File structure
• Top-level microservices/crates:
• dashboard/ → Next.js + React UI
• turbo-da-core/ → Core REST API service (Rust + Actix or Warp)
• db/ → Shared Diesel/Postgres database crate & migrations
• data_submission/ → Workload scheduler & data‐posting worker
• funds_monitor/ → Chain deposit/withdrawal indexing service
• fallback_monitor/ → Failed‐tx resubmission service
• contracts/ → Solidity/Foundry smart contracts for on-chain fee payments
• observability/ → OTEL collector & Prometheus config
• Shared config and Docker compose files orchestrate all these services locally or in production.
• Each Rust crate has its own Cargo.toml, src/, and env/config examples.
Key insights from README
• Core features: data submission to Avail, multi-token fee payment, user balance, rate limits, monitoring/resubmission.
• Each background service has its own environment variables, RPC endpoints, DB URL, and integration points.
• Observability is provided via OpenTelemetry + Prometheus.