What I work on

  • Data Platform Architecture

    Requirements, NFRs, architecture decisions, reference architectures and platform boundaries.

  • Microsoft Fabric & Data Engineering

    Lakehouse, Warehouse, pipelines, notebooks, Delta, integration and transformation.

  • SQL Server & Performance

    Production troubleshooting, Query Store, blocking, workload performance and migration.

  • Security, Resilience & Cost

    Identity, platform boundaries, recovery requirements, capacity and cost tradeoffs.

  • Observability & Operations

    Monitoring, execution logging, incident response, runbooks and operational ownership.

  • CI/CD & Delivery

    Source control, environments, release validation and production deployment.

Start here

Four pieces that show how I approach a platform: the first decisions, two moves from SQL Server and SSIS, and a production investigation.

How I think about architecture and engineering

Architecture is a set of decisions you can explain, test, measure and revisit. Good architecture makes systems easier to build, operate, recover and change, not just easier to draw.

  1. Start with the requirements

    Technology choices should follow the workload and its requirements, not trends.

  2. Measure before changing

    Performance work should begin with evidence.

  3. Design for operations

    Logging, deployment, debugging and recovery are part of the architecture.

  4. Keep complexity intentional

    More layers, services and abstractions are not automatically better.

  5. Build for change

    Data platforms, technologies and business requirements evolve.

  6. Share what you learn

    Explaining a problem often makes the solution better.

Why Javi Builds

I created Javi Builds to document the engineering lessons that are easy to lose when projects move on.

The goal is to turn practical experience into useful material for other engineers:

Some content starts with a simple question. Other pieces come from production problems, performance investigations, architecture tradeoffs or experiments.

The objective is the same: make complex data engineering problems easier to understand and apply.

Learn, build, share

Javi Builds is built around a simple idea: learning becomes more valuable when it is turned into something other people can use.

  1. LearnStudy a problem in depth
  2. BuildTurn it into working code
  3. PublishWrite it down clearly
  4. SharePresent it to others
  5. DiscussCompare notes with engineers
  6. ImproveFeed lessons back in
The cycle behind the site: each stage feeds the next, and discussion leads back to better work.

Where each stage lives on the site

What I'm exploring now

Areas of technical focus, with what this site already covers on each. They are interests and ongoing work, not a list of achievements.

Who this site is for

The same content serves two kinds of readers, from different angles.

Students & engineers learning

  • Understand concepts
  • Follow practical tutorials
  • Explore architecture
  • Build projects
  • Learn production thinking early

Experienced professionals

  • Compare architecture patterns
  • Study production tradeoffs
  • Improve performance
  • Reuse checklists and references
  • Discuss real engineering problems

Let's connect

Have a question, want to discuss a data platform or architecture problem, collaborate on a project, or invite me to speak?

Send me a message Connect on LinkedIn (opens in a new tab)