Where your app’s data lives, and how it gets there
Customers, invoices and bookings outlast any screen design. Microsive ATS uses all three: PostgreSQL and Prisma for its records, and Redis with BullMQ for its job queues.
Reviewed by: Rahul Jaiswar, founder
Where we use it
The product using all three is on the Microsive ATS page. PostgreSQL also stores data for other apps we build.
Records, access and short-lived data
- PostgreSQL is the system of record. Anything you’d be upset to lose goes here.
- Prisma is how TypeScript code reads and writes PostgreSQL, with typed queries and migration files.
- Redis holds data that can be rebuilt: job queues, counters, caches. Records stay out of it.
From save to storage
In a typical app, when someone saves a record, Prisma turns the TypeScript call into SQL and PostgreSQL stores it inside a transaction. Anything slow that the save triggers, such as an email, goes onto a Redis queue, and a worker handles it without holding up the screen.
Settle these early
Data choices are expensive to reverse, so settle two things before building: which records belong to which customer or team, and how timestamps and time zones are stored. The PostgreSQL page covers both, along with backups.
The code that uses this data is on the backend page, and where it runs is on the infrastructure page. For the service, see web apps, or browse all tools.
Records spread across sheets and inboxes?
Tell us what you track today and who needs to see it.