ENGINEERING / DATABASES
Every application has a different relationship with data. I enjoy exploring how databases store, organize and retrieve information, and how those decisions affect the systems built around them.
Back to engineeringStructure
How is the data organized?
Access
How will the application use it?
Consistency
What guarantees are needed?
Scale
How will it behave under load?
Choose the data model around the problem, not the other way around.
WHAT I'M EXPLORING
Different models. Different engineering decisions.
Working with structured data, relationships, constraints, and transactions. Designing schemas that preserve data integrity while supporting application requirements.
Modelling flexible, document-oriented data and understanding how access patterns influence document structure, indexing, and application design.
Representing highly connected data through nodes and relationships, making graph traversal and relationship-centric queries more natural.
Designing data access around application query patterns, with a focus on predictable performance, partitioning, and horizontal scalability.
Understanding what happens beneath database queries and making informed decisions around performance, consistency, concurrency, and reliability.
MY PERSPECTIVE
The best database is not necessarily the most powerful one. It is the one that fits the problem.
I believe database decisions should start with understanding the shape of the data, how the application accesses it, and the consistency and scalability requirements. Choosing a technology comes after understanding those trade-offs.
A SIMPLE WAY TO THINK ABOUT IT