Skip to content

Database Design & Optimization

I design data models for MySQL and PostgreSQL around the rules of the business, and I measure slow queries and speed them up. A well-built schema prevents most of the problems that would otherwise show up as an application grows.

The Regenix Health Center, Medical Expert Health, ART OTO AYNA and ARAS Elektrik projects all run on MySQL, and in Laravel projects I version the schema together with the code through migrations. I have also written on the blog about indexing, reading queries with EXPLAIN, transactions and locking.

What is included

  • Table and relationship design that follows the business rules
  • An indexing strategy and query analysis with EXPLAIN
  • Measuring and improving slow queries
  • Transactions and consistent data under concurrent access
  • Managing schema changes with migrations

Process

  1. I measure where things stand I study the schema and the most frequent and slowest queries.
  2. I find the bottlenecks I separate slowness caused by a missing index, by the shape of a query or by the data model.
  3. I improve and measure again I show the effect of every change with a before and after comparison.
  4. I document it I write down what changed and why, so your team can follow it later too.

Technologies

MySQL, PostgreSQL, SQL, Laravel, Eloquent

Frequently asked questions

Can my database be made faster without rebuilding it?

Often, yes: the right indexes and a few rewritten queries can make a clear difference. I measure first and show you where the bottleneck is, and we decide on the change together.

How are the timeline and the price decided?

By the scope of the work. I measure where things stand first, and base the quote, with the timeline and the price, on that measurement.