Service Architecture
Acceso is composed of internal services with strict domain ownership. This prevents tight coupling and enables independent scaling.
Service catalog
Failures stay contained inside a domain boundary.
Deploys can be staged service-by-service.
Performance tuning is localized to the hot service.
Why isolation matters
Gateway calls services through well-defined internal interfaces.
Services are responsible for business logic and upstream calls.
Shared infrastructure (like Redis) is used for cache and counters.
Communication model
Authentication and quotas.
Request validation.
Routing.
Standard response + error formatting.
The gateway owns:
Its upstream integrations.
Its parsing and adapter code.
Its normalization rules for that domain.
Its cache strategy and performance knobs.
Each service owns:
Service boundaries (domain ownership)
Last updated