Systems · Data · AI

Architecture for systems that have to remember correctly.

I’m Alexey Evlampiev, a Data Platform Architect in Eindhoven. I write field notes and essays about PostgreSQL, data platforms, and putting AI agents inside deterministic system boundaries.

Explore the essays About my work

The Lakehouse Publishes. Applications Decide Locally.

A reference architecture for exchanging governed data products through a lakehouse while keeping operational decisions local, transactional, and independently available.

Operational and Analytical Are Not Separate Architectures

Operational and analytical are not two architectures. They are the action and learning functions of one information ecosystem: applications observe and act, a shared substrate remembers and synthesizes, and knowledge returns to change the next decision.

Decoupling Compute and Storage in Postgres: The Architectural Implications of Databricks Lakebase

A vendor-neutral analysis of how Databricks Lakebase and the broader cloud-native PostgreSQL convergence fundamentally change what we can assume about database deployments.

Why We Are Still Getting Database Deployments Wrong in 2026: The Limits of External State Management

A technical analysis of why external migration tools structurally fail during complex PostgreSQL deployments, and what the alternative architecture looks like.