Skip to content

The arocapi boundary #75

Closed
Closed

Description

@johnf

Question

Which parts of the indexer are generic and belong in arocapi, and which stay in ldacapi? Candidates to move upstream: deriveUniqueEntityIds, pickSingleMemberOf, entityAsCrate, building file storage meta, shared-entity upserts, a meta.crateId index, OpenSearch index settings and per-call refresh as OpenSearchBackend options. LDaC-specific parts (profile filter, search fields and facets, ldac: handling) stay here.

Decide what to propose upstream, in what order, and what ldacapi does in the meantime. Filing upstream needs the maintainer's sign-off first.

Activity

  1. self-assigned this
    on Nov 17, 2026
  2. johnf commented on Nov 17, 2026

    @johnf
    CollaboratorAuthor

    Resolution

    Decided by grilling. No ADR and no glossary change: the decision is cheap to reverse and matches what arocapi already does.

    The boundary

    • arocapi stays read-only. ldacapi owns every write: entity and file rows, the crate↔entity links, and search documents. No crate-to-rows code is proposed upstream as part of this redesign.
    • Rejected: a small generic helper library upstream now; a full generic indexer upstream. arocapi closed its "crate exploder" issue (Write a "crate exploder" that can split a bundled crate into nice small parts crate-works/arocapi#1) deferring to ldacapi, and after the earlier decisions almost every candidate carries an LDaC rule.

    Where each candidate ended up

    Upstream

    In the meantime

    Kept liftable

    • The id rule and the file storage meta builder are plain functions with no LDaC imports, so they could move upstream if a second arocapi deployment ever needs them. No shared package and no profile-agnostic indexer core.

    Handed on

  3. johnf commented on Nov 17, 2026

    @johnf
    CollaboratorAuthor

    Input from "Oni aggregates: precompute or compute per request" (#73, resolved): aggregates are precomputed into a table of our own and read with one flat query per page from an entity transformer. arocapi never joins to that table. arocapi#142 (batch transformers) would replace the per-request microtask batching in src/oni.ts; nothing else is needed upstream for aggregates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions