Hi everyone,
I’ve been working with Neo4j to model fairly complex relationships, and while the graph side works well, I sometimes struggle with how execution logic is handled once things move outside the database. When multiple steps depend on graph queries, retries and execution order can get messy.
This came up in a chat where someone mentioned using a high quality /delta executor for android to manage execution flows in another context, which made me think more generally about this problem. How do you usually coordinate or trigger external execution logic that depends on neo4j results without losing traceability?
Do you rely on application-layer orchestration, background jobs, or something else to keep things predictable? Curious to hear how others approach this.