14 ms·
Having my app with direct write access to the scheduling backend could be... problematic from the separation of concerns. We'll have to deal with connection poo
by yandie 2y ago
Having my app with direct write access to the scheduling backend could be... problematic from the separation of concerns. We'll have to deal with connection pooling etc and we typically prefer to separate DB logic (interaction with postgres) from application logic.
Ignoring my setup, I'm a bit confused from the website if I can run this as a library? Seems that I need to use your SaaS backend to get started? Or did I misunderstand the flow from my quick flow?
- KraftyOne 2y agoFor separation of concerns/isolation, DBOS does all its bookkeeping in a separate Postgres database from your app database (documented here: https://docs.dbos.dev/explanations/system-tables https://docs.dbos.dev/explanations/system-tables). And yes, you can absolutely run this locally as a library! The bottom half of the quickstart covers how to do it: https://docs.dbos.dev/explanations/system-tables https://docs.dbos.dev/explanations/system-tables Just use a local (or Docker) Postgres.