F15.5 — Framework-neutral messaging core
| State | New |
| Parent | E15 |
| Tags | deferred |
| Predecessors | — |
| Source | E15 design, idea django-optional-areas (retired into E15) |
| Entry criteria | a SQLAlchemy application needs a transactional outbox or inbox (see the sqlalchemy-helpers and cloudevents-envelope ideas) |
No stories yet.
Split rn_forge.django.messaging into a neutral core and ORM bindings: the
relay loop, the consumer loop, UnknownMessageType and the field vocabulary on
OutboxStore and InboxStore protocols, with Django and SQLAlchemy stores as
adapters under the adapter structure.
Context
The design separates what is neutral from what is ORM-bound. The stores must supply a transaction scope, because the consumer records the processed marker in the same transaction as the handler. Only one binding exists today, so the neutral core would be designed against a single implementation. Whether the core is a new package or a part of commons is decided when this is scheduled, against ADR-0011.
Stories wait until the owner schedules the feature. Do not start or elaborate it before then.