HTAP is Dead
mooncake.dev
HTAP is Dead
1–10 of 95 posts
Re: HTAP is Dead
#2Re: HTAP is Dead
#3Why wouldn't it? The resources needed to run the backend of Cursor come from the compute for the AI models. Updating someone's quota in a database every few minutes is not going to be causing issues.
Re: HTAP is Dead
#4That is the worst smooth scrolling hijack I've ever seen, and the whole site breaks if you disable javascript.
Re: HTAP is Dead
#5https://learn.microsoft.com/en-us/azure/azure-sql/database/h...
Re: HTAP is Dead
#6> pg_mooncake is a PostgreSQL extension adding columnstore tables with DuckDB execution for 1000x faster analytics. Columnstore tables are stored as Iceberg or Delta Lake tables in your Object Store. Maintained by Mooncake Labs, it is available on Neon Postgres.
Seems to summarise the reason this article exists.
Not that I really disagree with the premise or conclusion of the article itself.
Re: HTAP is Dead
#7Re: HTAP is Dead
#8Re: HTAP is Dead
#9>Cursor is powered by a single-box Postgres instance Why wouldn't it? The resources needed to run the backend of Cursor come from the compute for the AI models. Updating someone's quota in a database every few minutes is not going to be causing issues.
Re: HTAP is Dead
#10>Cursor is powered by a single-box Postgres instance Why wouldn't it? The resources needed to run the backend of Cursor come from the compute for the AI models. Updating someone's quota in a database every few minutes is not going to be causing issues.