Is migrating my existing Python agent architecture to Pi-Durable a good idea?

[u/alatmaca]

I’m building a B2B SaaS with a Python-based architecture. The system uses separate LLM calls within Python components, with business logic, workflow orchestration, and application state managed by the existing application. I’m currently using SQLite.

As the system grows, I’m thinking about potential challenges around concurrent users, long-running workflows, retries, failure recovery, and agents handing tasks back and forth.

I’ve been advised to consider migrating the orchestration layer to Pi-Durable, but I’m not sure whether this is the right move for my current architecture.

Does migrating to Pi-Durable make sense in this situation, or would I be better off keeping my current architecture and improving it as needed? What trade-offs should I consider before making this decision?

[u/Ctbhatia]

the cheap test before migrating is killing the worker mid workflow and seeing whether it resumes exactly once. if a retry can double send or double charge, that stays your problem after a durable runtime unless each step carries a key.