Back end is full of hidden workflows
4 days ago
- #system-architecture
- #workflow-management
- #backend-development
- Backend systems gradually evolve from simple request handlers into complex workflows involving retries, queues, callbacks, and coordination across services.
- Hidden workflows emerge from incremental decisions (like adding retries or queues) that interconnect over time, making systems harder to understand, debug, and modify.
- Workflows exist inherently when actions depend on each other, regardless of formal acknowledgment; visibility is key to managing them effectively.
- Common examples include signup flows, order processing, and support ticketing, where steps like validation, notifications, and integrations create orchestration.
- Hidden workflows lead to expensive changes, painful debugging, and eroded team trust due to distributed logic and reliance on tribal knowledge.
- Explicit workflows improve clarity by centralizing coordination, making steps, decisions, and dependencies visible, easing maintenance and troubleshooting.
- Unmeshed is presented as a solution to define and manage workflows explicitly, reducing hidden complexity without replacing existing services.