31–40 of 187 posts
A lot of congrats and excitement, questions about who uses it in a production environment, very specific use-case questions, and of course the name.
Weird how predictable the response to one company/tech always is.
I will never use this product no matter how good it is due to its name. Hope you can understand that many ppl like me suffer phobia from cockroaches. (PS: As expected ppl will downvote this, but just trying to give a very valuable feedback to ppl who don’t understand cockroach phobia.)
That's unfortunate, but I hope your post isn't suggesting they shouldn't have named their product as they did. Should people who don't like large numbers not use Google? Should people who fear fire not use Firebase? Should people who don't like coffee not use Java? Moreover, should those people suggest the names be changed due to their phobia? We could number all database servers. Server 1, Server 2, Server 3, Server…
I will never use this product no matter how good it is due to its name. Hope you can understand that many ppl like me suffer phobia from cockroaches. (PS: As expected ppl will downvote this, but just trying to give a very valuable feedback to ppl who don’t understand cockroach phobia.)
Granted, phobias are no fun and can be debilitating but seeing as the product has been around for 3 yrs, I don't think they have any plans on renaming it. Quick question, and don't take it the wrong way as I am truly trying to understand the extend of your commitment of not using it, but what if you were to receive a once in a lifetime job offer and after you start the team decided to switch to this database, would y…
Im not sure what will happened to my job but given an equal choice i would choose alternatives, job or database.
Great stuff. I appreciated being educated about TPC-C, and the whole spirit of not focusing on vanity benchmarks!
edit: Looking into it even further, I agree with the co-author's response here that TPC-C is still an appropriate metric. TPC-E is different and newer but still not as widely used.
I will never use this product no matter how good it is due to its name. Hope you can understand that many ppl like me suffer phobia from cockroaches. (PS: As expected ppl will downvote this, but just trying to give a very valuable feedback to ppl who don’t understand cockroach phobia.)
That's unfortunate, but I hope your post isn't suggesting they shouldn't have named their product as they did. Should people who don't like large numbers not use Google? Should people who fear fire not use Firebase? Should people who don't like coffee not use Java? Moreover, should those people suggest the names be changed due to their phobia? We could number all database servers. Server 1, Server 2, Server 3, Server…
Earlier quoted context omitted.
We use Citus and Memsql (big data analytics use cases). How does Cockroach handle joins and other OLAP style queries?
You're not going to get better performance for OLAP than MemSQL's columnstore and in-memory rowstore for reference tables to join. Citus is great if you want the Postgres interface but is still using standard rowstore tables. CockroachDB is similar with rowstore performance but with added distributed consensus overhead. They are both much better for OLTP and sharding. CockroachDB also provides easy high-availability…
Earlier quoted context omitted.
Granted, phobias are no fun and can be debilitating but seeing as the product has been around for 3 yrs, I don't think they have any plans on renaming it. Quick question, and don't take it the wrong way as I am truly trying to understand the extend of your commitment of not using it, but what if you were to receive a once in a lifetime job offer and after you start the team decided to switch to this database, would y…
Yes just hearing or reading the word “cockcroach” gives me a cringe. I tried to google the word “cockroach phobia” just now and damn google shows a bunch of cockroach images that made me press back button immediately and couldn’t read a damn thing. Im not sure what will happened to my job but given an equal choice i would choose alternatives, job or database.
Earlier quoted context omitted.
You're not going to get better performance for OLAP than MemSQL's columnstore and in-memory rowstore for reference tables to join. Citus is great if you want the Postgres interface but is still using standard rowstore tables. CockroachDB is similar with rowstore performance but with added distributed consensus overhead. They are both much better for OLTP and sharding. CockroachDB also provides easy high-availability…
MemSQL is one of those "ask for a quote" products. What are some rule of thumb estimates for what it costs?
How is this meaningful without detailed setup description? http://www.tpc.org/tpcc/results/tpcc_results.asp?print=false... Looking at this list of results one wonders what those results actually mean?
"Note: We have not filed for official certification of our TPC-C results. However, we will post full reproduction steps in a forthcoming whitepaper."
Before clicking the comments link, I always know what to expect in HN comment section for a CDB post announcing their latest milestone or feature: A lot of congrats and excitement, questions about who uses it in a production environment, very specific use-case questions, and of course the name. Weird how predictable the response to one company/tech always is.