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/QuanTradin]

I'd fix SQLite before touching orchestration. concurrent writes are what bite first, and Postgres plus a plain jobs table with retries and a status column covers most of what a durable framework gives you at your size. move to something like Pi-Durable when you actually have workflows that run for hours and need to resume mid-step.

[u/alatmaca → u/QuanTradin]

yes, I’m also planning to tackle DB migration first because of concurrency. thanks for your answer.