1.0.0-rc.1 · Release Candidate2 min read
Application Topology
Understand the responsibilities and boundaries of AutoCore Web, Admin, API, Worker, and infrastructure services.
| Component | Responsibility | Must not do |
|---|---|---|
| Web | Public marketplace and buyer/seller presentation | Own server-side business rules or direct database access |
| Admin | Authenticated marketplace, catalog, legal, payment, and system operations | Bypass API authorization or expose secrets |
| API | Validation, authorization, domain services, persistence, and versioned contracts | Delegate authority to client state or search projections |
| Worker | Queue-backed media, indexing, notification, email, and scheduled work where enabled | Become an unobserved second source of truth |
| PostgreSQL | Durable relational state through Prisma | Be replaced by a derived index |
| Redis | Queue, cache, and short-lived coordination roles proven by each module | Be documented as every possible queue/cache/session role without evidence |
| Meilisearch | Query, filter, sort, and facet projection | Be treated as authoritative listing state |
| Media storage | Binary objects behind a provider abstraction | Expose raw storage paths or provider credentials |
Topology flow
- A client sends a versioned API request through the public routing boundary.
- The API validates input and authenticated scope.
- Domain services read or write PostgreSQL and emit audit or side-effect work.
- An enabled Worker path processes asynchronous work and updates derived state.
- The client receives a stable contract; it does not learn provider secrets or internal network identifiers.
The future mobile application is an API client, not a separate business-logic implementation. Native mobile completion is not claimed by this documentation.
Related articles
Installation IsolationUnderstand the data, namespace, and service boundaries that keep AutoCore installations separate.System OverviewRead the source-verified AutoCore system context and responsibility boundaries.Request and Data FlowFollow public, Admin, and API request lifecycles through AutoCore’s validation, authorization, and persistence boundaries.Background ProcessingUnderstand AutoCore queue, Worker, indexing, media, notification, and scheduled-processing boundaries.