FractionalDataArchitect
Book a discovery call

Too Deep Into Snowflake" Is an Architecture Smell

Too Deep Into Snowflake" Is an Architecture Smell
Too Deep Into Snowflake" Is an Architecture Smell

You can measure architecture health by the price of an exit. For one stack I reviewed, it was 18 months.

The exit cost accumulated one default at a time: business logic in stored procedures, vendor-specific SQL in 400 models, tasks and streams doing the orchestration, no contracts at the boundaries.

Each choice was locally sensible. Snowflake is a good warehouse. That’s what makes the pattern quiet.

The smell shows up when every future decision carries the vendor’s price tag: the renewal negotiation, the new AI workload, the acquisition due diligence. An 18-month exit means you negotiate with no walk-away option, and the other side usually knows.

What usually keeps optionality alive:

  1. Transformation logic in portable SQL, not proprietary procedures.
  2. Orchestration outside the warehouse.
  3. Contracts at the edges, so consumers don’t care what’s behind them.

You probably shouldn’t leave. Being credibly able to changes the conversation.

What would your exit estimate be if someone asked for it this quarter?

Written by Thomas Nys

Fractional Data Architect helping startups and scaleups build data platforms that scale.

More about Thomas Nys →

Recognise the problem? Let's talk about it.