Separate crypto compute role (--target=crypto) for independent scaling #33
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Cordy/Cairn#33
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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=cryptoreplica (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.