MySQL

Relational schema design, transaction management, query optimization, and storage engine configuration.

1 / Early Database Experience

MySQL was one of the first relational databases I worked with. Its role in my projects was limited compared to PostgreSQL, which became my default for production applications. MySQL provided a straightforward environment for learning relational schema design, transaction management, and query optimization fundamentals.

2 / Honest Scope

I understand MySQL's storage engine architecture (InnoDB vs MyISAM), its transaction isolation levels, and its query optimizer behavior at a functional level. However, my production database experience is predominantly PostgreSQL. When I choose a relational database for a new project, PostgreSQL's extensibility — particularly pgvector for Vector Embeddings and JSONB for semi-structured data — makes it the more practical choice for the kinds of systems I build.