Service Boundaries & Responsibilities
Owns request safety and consistency.
API Gateway (public edge)
Boundary map
Acceso is split into bounded services to keep failures contained. This also keeps iteration fast per domain.
Auth and API key validation.
Quotas, rate enforcement, abuse controls.
Parameter validation and routing.
Error standardization and response wrapping.
Request identifiers and telemetry propagation.
Why this split is non-negotiable
Solana service
Chain reads, transaction parsing, token/account primitives.
DeFi analytics service
Protocol adapters, trades, liquidity, OHLCV, derived analytics.
Polymarket service
Markets, orderbooks, prices, trades, history.
Zero-knowledge proof service
Proof generation, verification, circuit execution.
x402 payment service
Micropayment negotiation, settlement, facilitator coordination.
Notification service
WebSocket streams, webhook delivery, retry logic.
Domain responsibilities (at a glance)
Redis caching.
Observability pipeline (logs, metrics, tracing).
Deployment primitives and runtime safety controls.
Shared infra (cross-cutting)
Upstream interaction and failover policy.
Parsing, decoding, and normalization.
Caching and derived views for that domain.
Domain-specific metrics and health signals.
Own domain logic and upstream dependencies.
Domain services (protocol + product domains)
Does not own protocol-specific parsing. It forwards to domain services.
Fault isolation: upstream failures stay within one domain.
Independent scaling: hot domains scale without global overprovisioning.
Clear ownership: each domain has one place to fix parsing and caching bugs.
Last updated