3 ms·
I would be curious to know if anyone tried using one of the newer data-warehouse databases (Clickhouse, Snowflake, etc) as an OLTP database, to run their crud a
by yen223 2y ago
I would be curious to know if anyone tried using one of the newer data-warehouse databases (Clickhouse, Snowflake, etc) as an OLTP database, to run their crud app.
- hodgesrm 2y agoYou can't use ClickHouse this way. It does not have ACID transactions and the main table type (MergeTree) is optimized for reads on append-only workloads that operate on large blocks. MySQL & PostgreSQL are vastly better for OLTP use cases.
- yen223 2y agoI know that you shouldn't, but I'm curious if anyone did. I don't think it is impossible to use Clickhouse as a backend to a CRUD app, if you didn't particularly care about things like transactional guarantees or read performance. You still can write rows to it, and read rows from it. I've also worked in the business long enough to know that people make all kinds of suboptimal engineering decisions all the time.
- altdataseller 2y agoI’m sure some people do. Just simply because ppl do all sorts of things they shouldn’t do.
- kirubakaran 2y agoThe Rule 34 of system design
- kwillets 2y agoWe came close, as we had architects who knew little besides Snowflake. While there are all kinds of issues it can't handle for CRUD, such as locking and small updates, it's also expensive to do small reads due to the reliance on auto-scaling instead of timesharing. If your app pageloads and issues dozens of queries to populate its widgets, SF will be both slow and expensive.