eho/register-referentie
1
0
Fork 0
Code Issues 10 Pull Requests 1 Actions Packages Projects Releases 1 Wiki Activity

ADR proposal · External-task job-worker pattern for the Domain Service ↔ Flowable #60

New Issue
Closed
opened 2026-06-30 14:48:18 +00:00 by not · 0 comments
not commented 2026-06-30 14:48:18 +00:00
Contributor
Copy Link
Copy Source

Context

S-05 (#6) introduces the BIG Domain Service, which must orchestrate: start a Flowable registratie process → the OpenZaakAanmaken external task executes the ACL OpenZaak → the zaak URL is stored on the Registration aggregate.

The BPMN OpenZaakAanmaken task is a Flowable external-worker service task (S-03). Something has to acquire/lock that job, do the work, and complete it. This is an ADR-worthy moment per CLAUDE.md §14 (a service boundary is defined; the Workflow Client↔Flowable coupling rule §8.2 is exercised).

Decision to record

The Workflow Client (Infrastructure of the Domain Service) is the only code that talks to Flowable (§8.2). It acts as an external-task job worker (PRD §36): a hosted background worker polls Flowable for OpenZaakAanmaken jobs, locks one, calls the ACL to open a zaak (§8.1 — only the ACL talks to ZGW), attaches the resulting zaak URL to the aggregate, and completes the job. Orchestration is therefore eventually consistent, not request-synchronous.

Options considered

  • A — Hosted background job worker (proposed). Matches PRD §36 and the Flowable external-worker model; decouples the submit request from ACL latency.
  • B — Synchronous acquire+complete inside the POST /registrations request. Simpler/deterministic but couples the request to ACL latency and is not the documented pattern.

Consequences

  • The worker logic lives in Application (testable against fake ports); the polling loop is a thin BackgroundService in Infrastructure.
  • Registration persistence is in-memory for the minimal slice (the read path is fed by NRC→projection from #7); an EF-backed domain store is a documented follow-up.

ADR file docs/architecture/adr-0009-external-task-job-worker.md lands in the PR that implements #6.

## Context S-05 (#6) introduces the BIG Domain Service, which must orchestrate: start a Flowable `registratie` process → the `OpenZaakAanmaken` external task executes the ACL `OpenZaak` → the zaak URL is stored on the Registration aggregate. The BPMN `OpenZaakAanmaken` task is a Flowable **external-worker** service task (S-03). Something has to acquire/lock that job, do the work, and complete it. This is an ADR-worthy moment per CLAUDE.md §14 (a service boundary is defined; the Workflow Client↔Flowable coupling rule §8.2 is exercised). ## Decision to record The **Workflow Client** (Infrastructure of the Domain Service) is the *only* code that talks to Flowable (§8.2). It acts as an **external-task job worker** (PRD §36): a hosted background worker polls Flowable for `OpenZaakAanmaken` jobs, locks one, calls the ACL to open a zaak (§8.1 — only the ACL talks to ZGW), attaches the resulting zaak URL to the aggregate, and completes the job. Orchestration is therefore eventually consistent, not request-synchronous. ## Options considered - **A — Hosted background job worker (proposed).** Matches PRD §36 and the Flowable external-worker model; decouples the submit request from ACL latency. - **B — Synchronous acquire+complete inside the POST /registrations request.** Simpler/deterministic but couples the request to ACL latency and is not the documented pattern. ## Consequences - The worker logic lives in Application (testable against fake ports); the polling loop is a thin `BackgroundService` in Infrastructure. - Registration persistence is in-memory for the minimal slice (the read path is fed by NRC→projection from #7); an EF-backed domain store is a documented follow-up. ADR file `docs/architecture/adr-0009-external-task-job-worker.md` lands in the PR that implements #6.
not added the type:adr-proposalarea:domainarea:workflow labels 2026-06-30 14:49:47 +00:00
not closed this issue 2026-07-01 08:46:22 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area:acl
area:bff
area:docs
area:domain
area:event-subscriber
area:infra
area:portal-behandel
area:portal-beheer
area:portal-openbaar
area:portal-self-service
area:projection
area:workflow
type:adr-proposal
type:bug
type:chore
type:slice
No labels area:domain area:workflow type:adr-proposal
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
eho (Edwin van den Houdt)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: eho/register-referentie#60