Database Solutions
Data modelling, query and index optimisation, migrations and analytics pipelines. Most performance problems and most data-integrity bugs are decided at schema design time, long before they are noticed.
What this covers
Correctness in the schema
Constraints, foreign keys and exact numeric types for money. Integrity belongs in the database, not in every code path that remembers to check.
Query and index work
Execution plans read properly, indexes chosen for real access patterns, and N+1 queries found before they reach production traffic.
Migrations without downtime
Reversible, reviewed migrations with a strategy for large tables, so a schema change is not an outage.
Analytics separated from serving
Reporting workloads kept off the transactional database, so a heavy dashboard query cannot slow down checkout.
Have a database solutions project?
Tell us the problem and the constraints you are working within. We will come back with how we would approach it.
Start a conversationFrom the notes
- The shop's day is not the server's dayA report grouped by the database's UTC day counts every bill before 05:30 IST against yesterday. The query that was wrong, and the query that is right.
- Decimal vs float for money, from a billing systemMoney is a string at rest, a float at the counter and an integer at the gateway. Three representations in one billing system, and what happens at the seams.