Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Citus 6.2: Concurrent index creation and complex queries for multi-tenant dbs

citusdata.com

Post reply on HN
Print view View original

11–17 of 17 posts

Re: Citus 6.2: Concurrent index creation and complex queries for multi-tenant dbs

#11

Post by SwellJoe »

erikpukinskis wrote: post #9

Just a quick comment on this: > Good software never stops evolving I think I would translate this as: "our software is so large in scope, it must never stop evolving if it is to remain good enough." Small software, with a single, focused goal, can evolve to a steady state which is still good. Often we need to build things whose scope is too large for that, and must constantly churn. That's ok. But ideally you are fin…

That's kinda vague philosophizing about an actual project. It seems pretentious and not constructive.

Do you have a concrete criticism of Citus? Do you believe a database system can become your definition of "God", or are large database systems simply not necessary and could be replaced by a few tiny God-like pieces? If so, why do large database systems exist at all?

Re: Citus 6.2: Concurrent index creation and complex queries for multi-tenant dbs

#12

Post by threeseed »

old-gregg wrote: post #3

Citus people are putting SQL back into NoSQL! :) Awesome.

SQL has actually been back in NoSQL for a few years now.

Spark SQL, Presto, Vora for example allow you to write ANSI SQL and query NoSQL stores such as Cassandra, HBase, MongoDB etc.

And if you are are after SQL-Like well then you have Phoenix, Hive, CQL etc.

Re: Citus 6.2: Concurrent index creation and complex queries for multi-tenant dbs

#13

Post by qaq »

jumanjisama wrote: post #7
qaq wrote: post #5

Do you guys have pricing anywhere on the site?

Not them, but here is the link for their cloud offering https://www.citusdata.com/pricing For other enterprise solution would require you to contact them first.

hmm 200K/month for 20 HA nodes with 20TB and 4TB RAM. A bit pricy and 20TB is kindah low for max disk. A single PG instance on a hefty box can do 20TB.

Re: Citus 6.2: Concurrent index creation and complex queries for multi-tenant dbs

#14

Post by jumanjisama »

qaq wrote: post #13
jumanjisama wrote: post #7

Earlier quoted context omitted.

Not them, but here is the link for their cloud offering https://www.citusdata.com/pricing For other enterprise solution would require you to contact them first.

hmm 200K/month for 20 HA nodes with 20TB and 4TB RAM. A bit pricy and 20TB is kindah low for max disk. A single PG instance on a hefty box can do 20TB.

It comes with more than just the database. The package includes, but not limited to:

  1. All enterprise features.
  2. All nodes being managed by Citus themselves. All the upgrades or rebalancing will be done by them.
Another option which should be cheaper is paying for the Enterprise license and manage it on your own hardware with your own setup.

Finally, you could also spin up the community version, which is free but lack important enterprise features such as rebalancing the shards when you add more nodes to the setup.

Re: Citus 6.2: Concurrent index creation and complex queries for multi-tenant dbs

#15

Post by craigkerstiens »

qaq wrote: post #13
jumanjisama wrote: post #7

Earlier quoted context omitted.

Not them, but here is the link for their cloud offering https://www.citusdata.com/pricing For other enterprise solution would require you to contact them first.

hmm 200K/month for 20 HA nodes with 20TB and 4TB RAM. A bit pricy and 20TB is kindah low for max disk. A single PG instance on a hefty box can do 20TB.

Craig from Citus here, if disk is your biggest bottleneck we do have some flexibility there and can go larger than 1 TB per node if needed. Or it may be that Citus isn't the best tool for you as well.

In general what we find is most Citus users are either memory constrained or constrained on processing power.

Re: Citus 6.2: Concurrent index creation and complex queries for multi-tenant dbs

#16

Post by qaq »

jumanjisama wrote: post #14
qaq wrote: post #13

Earlier quoted context omitted.

hmm 200K/month for 20 HA nodes with 20TB and 4TB RAM. A bit pricy and 20TB is kindah low for max disk. A single PG instance on a hefty box can do 20TB.

It comes with more than just the database. The package includes, but not limited to: 1. All enterprise features. 2. All nodes being managed by Citus themselves. All the upgrades or rebalancing will be done by them. Another option which should be cheaper is paying for the Enterprise license and manage it on your own hardware with your own setup. Finally, you could also spin up the community version, which is free but…

Thank you for all the info the use case we are running a setup with dedicated PG RDS instance for each client some of them are pushing the RDS limits of 6TB potentially looking to move to multi tenant setup as managing 100+ instances is not fun. The read load is fairly light it's rare that more than a few people are running queries against an instance. Would it be possible to consolidate using Citus (are there any advantages as far as ease of management etc?)

Re: Citus 6.2: Concurrent index creation and complex queries for multi-tenant dbs

#17

Post by erikpukinskis »

SwellJoe wrote: post #11
erikpukinskis wrote: post #9

Just a quick comment on this: > Good software never stops evolving I think I would translate this as: "our software is so large in scope, it must never stop evolving if it is to remain good enough." Small software, with a single, focused goal, can evolve to a steady state which is still good. Often we need to build things whose scope is too large for that, and must constantly churn. That's ok. But ideally you are fin…

That's kinda vague philosophizing about an actual project. It seems pretentious and not constructive. Do you have a concrete criticism of Citus? Do you believe a database system can become your definition of "God", or are large database systems simply not necessary and could be replaced by a few tiny God-like pieces? If so, why do large database systems exist at all?

I have no criticism of Citus at all. Seems like a great project.

I don't think systems of large scope can necessarily be replaced by small scope ones. Just that the large project is probably suffering if smaller, more stable parts aren't sloughing off of it as part of your device process.

Post reply on HN