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

Data Stores

Understand what PostgreSQL, Redis, Meilisearch, and media storage own in the AutoCore architecture.

StoreAuthority or roleRecovery/consistency implication
PostgreSQLAuthoritative transactional records for installation, users, catalog, listings, policies, consent, payments, and auditData changes must be validated and persisted here before derived work is trusted.
RedisQueue, cache, and short-lived coordination state where a module explicitly uses itLoss can require requeue, cache rebuild, or fallback; it is not the marketplace record source.
MeilisearchDerived listing document projection for text, filters, facets, and sortingDrift or outage is handled through fallback/reindex concepts.
Media storageBinary originals and generated objects behind a provider interfaceMetadata and binary availability can diverge; processing and deletion require reconciliation.

Search indexing flow

  1. PostgreSQL listing state changes.
  2. The API requests a search-document sync.
  3. The index service maps safe listing facts into a flat document.
  4. Meilisearch updates or removes the projection.
  5. Public search uses the projection when healthy and PostgreSQL when degraded.

Media processing flow

  1. A validated upload creates or updates a media metadata record.
  2. The image service cleans orientation and metadata and generates variants.
  3. The storage provider persists the original and derivative objects.
  4. The record becomes ready or retains a failed processing state.
  5. Listing/dealer surfaces consume approved public variants only.

No production bucket, index name, database URL, or host identifier belongs in this public architecture page.

Related articles

Media DomainUnderstand AutoCore media assets, processing states, variants, ownership, storage, and failure boundaries.Search and IndexingLearn how AutoCore uses PostgreSQL as truth and Meilisearch as a derived public search projection.System OverviewRead the source-verified AutoCore system context and responsibility boundaries.Background ProcessingUnderstand AutoCore queue, Worker, indexing, media, notification, and scheduled-processing boundaries.