Description

The database is where architectural problems become visible usually once it's already too late. I'm a database administrator as well as a developer, and that combination matters: I model data thinking about how it will be queried in three years, not just how it will be stored today. I work both on greenfield design and on rescuing systems that have stopped keeping up with growth.

What's Included

• Data Modelling: Normalised relational schema design, with denormalisation decisions justified by real query patterns.

• Performance Optimisation: Slow query analysis, indexing strategy, configuration tuning and rewriting problematic queries.

• Multi-Tenant Architecture: Selecting and implementing the right isolation strategy discriminator column, schema-per-tenant or dedicated database.

• Backup and Recovery: Backup policy with clear recovery point and recovery time objectives, and regular restore testing.

• Migrations: Migration between database systems and between servers, planned to minimise or eliminate downtime.

• Geospatial Data: PostGIS implementation for high-performance geographic queries, including proximity search and distance calculation.

Technologies

• Relational: MySQL, MariaDB, PostgreSQL with PostGIS, SQL Server and Oracle.

• Tooling: Execution plan analysis, performance monitoring tools and change audit systems.