Separate crypto compute role (--target=crypto) for independent scaling #33

Open
opened 2026-07-25 17:44:14 +00:00 by Cordy · 0 comments
Owner

Manuel clarified the reason for a separate encryption service in his sketch: prevent a compute choke under many concurrent users and scale crypto independently of frontend/backend — not just abstraction.

Our current answer (in-binary decorator + --target= role flags, ARCHITECTURE §9) is a code seam, not yet a separable replica. Make the encrypt/decrypt role genuinely runnable as its own --target=crypto replica (Loki/MinIO/Vault single-binary-many-roles pattern) so an operator can scale it apart from the rest — honoring his intent without splitting the codebase.

Manuel clarified the *reason* for a separate encryption service in his sketch: **prevent a compute choke** under many concurrent users and **scale crypto independently** of frontend/backend — not just abstraction. Our current answer (in-binary decorator + `--target=` role flags, ARCHITECTURE §9) is a code seam, not yet a separable replica. Make the encrypt/decrypt role genuinely runnable as its own `--target=crypto` replica (Loki/MinIO/Vault single-binary-many-roles pattern) so an operator can scale it apart from the rest — honoring his intent without splitting the codebase.
Sign in to join this conversation.
No labels
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#33
No description provided.