upvote
Agree with everything here. Workload isolation and independent scaling in particular are the reasons I never see HTAP work out in practice, even beyond expected loss from not using the more specialized solution. A very low latency storage handoff between two engines always seems like 80% of value with 20% of operational headache.
reply
The workloads are different. An almost -in-sync analytics replica is a decent tradeoff (copy, lag etc).

I'm working on one such solution right now,

reply
> HTAP has historically been niche because the cost of analytics on fresh data wasn't worth the squeeze (sooner or later the MBAs step in). Separating the OLTP and OLAP layers gives you better workload isolation and the ability to optimize each independently.

That feels like something HTAP databases could offer as a choice!

- Things you can always do

- Things you can do when optimizing for fresh data

- Things you can do when optimizing for analytics on old data

- Things you can do, but with poor performance

This feels like one of those cases where people choose to make software simple instead of, and at the cost of (not) making operations simple.

reply
You are correct! And sadly the vast majority of people don't want to make choices or think about that tradeoff.

If it can't outperform pure OLTP and it can't outperform pure OLAP then there is no pit of success for such an HTAP system.

The unfortunate part is that the vast majority of software out there in the world would be served perfectly with an HTAP solution.

The fortunate part is that for a lot of problems you can just run Postgres and then when you need analytics you can still use Postgres, until you hit scaling issues (if ever).

I've never seen a project choose to solve OLAP and OLTP upfront and succeed.

reply