I'm working on one such solution right now,
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.
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.