Live data from Hacker News

Is an All-in-One Database the Future?

news.ycombinator.com

11–12 of 12 posts

Re: Is an All-in-One Database the Future?

#11
post #4

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.

We 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.

Re: Is an All-in-One Database the Future?

#12
post #7

Earlier quoted context omitted.

I 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.

I’m sure some people do. Just simply because ppl do all sorts of things they shouldn’t do.

The Rule 34 of system design
Post reply on HN