Transactional data
Orders, payments, bookings, stock: everything that must be exact, not approximately exact.
DATABASE
PostgreSQL
The database that does not lose your data.
PostgreSQL is an open-source relational database, used for over thirty years by banks, governments and most large web platforms. It stores your data in a structured way and guarantees that an operation either completes entirely or not at all — a payment cannot be half-recorded, even if the server dies at the worst moment.
What it guarantees you
- No partial writes: an order is stored whole or rolled back cleanly
- Fast full-text search without adding a second tool to maintain
- JSON where the shape must stay flexible, relational where it must stay strict
- No licence cost, and no risk of being locked to a vendor
What we put in it
Content search
Catalogues, document stores, internal engines: built-in full-text search is enough in the large majority of cases.
Semi-structured data
Forms with variable fields, preferences, metadata: the JSON type avoids multiplying tables for no reason.
What it does not do
PostgreSQL is not a cache: for extremely frequent reads of the same value you need a dedicated layer in front. It is also not built for analytics over billions of rows, where a data warehouse fits better. And it must be tuned: a badly indexed database will be slow no matter how good the engine is.
Where we stand
PostgreSQL is our default, and we rarely move off it. Most projects that think they need an exotic database actually need correct indexes.
A slow or fragile database?
We review your schema, your indexes and your slow queries, then hand back a costed remediation plan.
Request a database auditOther pieces of the stack