Skip to content
mcorucu docs
AutoCore1.0.0-rc.1 · Release Candidate
1.0.0-rc.1 · Release Candidate2 min read

System Overview

Read the source-verified AutoCore system context and responsibility boundaries.

AutoCore follows an API-first, event-oriented modular-monolith architecture. Web and Admin are clients; the API owns business logic and persistence; Worker processing handles work that should not block interactive requests.

System context

Code
Public browser or future mobile client
        │
        ▼
Web or Admin surface
        │ versioned HTTP/JSON API
        ▼
API domain modules ──> PostgreSQL transactional state
        │              ├─> Redis transient/queue coordination
        │              ├─> Meilisearch derived search projection
        │              └─> media storage abstraction
        ▼
Worker jobs and external providers where enabled

The reverse proxy is an exposure and TLS boundary. It does not replace API authentication or authorization. External email, storage, monitoring, and payment services are configuration boundaries, not bundled guarantees.

AutoCore system topology showing public clients, Web and Admin, the versioned API, PostgreSQL, Redis, Meilisearch, and Worker processing

Text alternative: public clients reach Web or Admin; those surfaces call the versioned API. The API owns PostgreSQL state and coordinates Redis, Meilisearch, media storage, and bounded Worker processing.

Authority and derivation

PostgreSQL owns installation, identity, catalog, listing, policy, consent, payment, and audit records. Redis stores transient or coordination state where the current module uses it. Meilisearch and media variants are derived or processed representations that can become delayed or unavailable without changing the transactional source.

This page intentionally uses a text system map rather than Mermaid or a fictional screenshot. The relationships are source-verified and remain readable on mobile and in dark mode.

Related articles

Application SurfacesSee how AutoCore Web, Admin, API, Worker, data stores, search, and reverse proxy fit together.Application TopologyUnderstand the responsibilities and boundaries of AutoCore Web, Admin, API, Worker, and infrastructure services.Data StoresUnderstand what PostgreSQL, Redis, Meilisearch, and media storage own in the AutoCore architecture.Security and Configuration BoundariesUnderstand AutoCore authentication, authorization, installation, edition, configuration, and external-service boundaries.