CockroachDB: A Scalable, Geo-Replicated, Transactional Datastore

#1

Post by sokrates » Fri, May 30, 2014, 5:49 PM UTC

CockroachDB: A Scalable, Geo-Replicated, Transactional Datastore
github.com

Re: CockroachDB: A Scalable, Geo-Replicated, Transactional Datastore

#2

Post by limsup » Fri, May 30, 2014, 6:16 PM UTC

I assume it's called this because a cockroach can supposedly survive a nuclear attack. But it's a bad name. It does not invoke good feelings.

Re: CockroachDB: A Scalable, Geo-Replicated, Transactional Datastore

#3

Post by oalders » Fri, May 30, 2014, 6:18 PM UTC

limsup wrote: post #2

I assume it's called this because a cockroach can supposedly survive a nuclear attack. But it's a bad name. It does not invoke good feelings.

It's memorable and I think the meaning is pretty clear, but it did make me shudder as well. :)

Re: CockroachDB: A Scalable, Geo-Replicated, Transactional Datastore

#4

Post by taternuts » Fri, May 30, 2014, 6:19 PM UTC

limsup wrote: post #2

I assume it's called this because a cockroach can supposedly survive a nuclear attack. But it's a bad name. It does not invoke good feelings.

I have to agree - maybe 'RoachDB' would be better

Re: CockroachDB: A Scalable, Geo-Replicated, Transactional Datastore

#5

Post by morgante » Fri, May 30, 2014, 6:22 PM UTC

taternuts wrote: post #4

limsup wrote: post #2

I assume it's called this because a cockroach can supposedly survive a nuclear attack. But it's a bad name. It does not invoke good feelings.

I have to agree - maybe 'RoachDB' would be better

I like RoachDB. The idea is still there, but it's a little more fun.

Re: CockroachDB: A Scalable, Geo-Replicated, Transactional Datastore

#6

Post by donut2d » Fri, May 30, 2014, 6:25 PM UTC

limsup wrote: post #2

I assume it's called this because a cockroach can supposedly survive a nuclear attack. But it's a bad name. It does not invoke good feelings.

Have to agree. I have so many bad feelings attached to cockroaches that just seeing the name makes me sick to my stomach.

Re: CockroachDB: A Scalable, Geo-Replicated, Transactional Datastore

#7

Post by gresrun » Fri, May 30, 2014, 6:26 PM UTC

limsup wrote: post #2

I assume it's called this because a cockroach can supposedly survive a nuclear attack. But it's a bad name. It does not invoke good feelings.

Trademark considerations aside, I'd vote for TwinkieDB

Re: CockroachDB: A Scalable, Geo-Replicated, Transactional Datastore

#8

Post by notduncansmith » Fri, May 30, 2014, 6:28 PM UTC

limsup wrote: post #2

I assume it's called this because a cockroach can supposedly survive a nuclear attack. But it's a bad name. It does not invoke good feelings.

Maybe "Caracha" or "CarachaDB"? As in, "La Cucaracha". Still there, but veiled enough that it won't make people uncomfortable just on hearing it.

Re: CockroachDB: A Scalable, Geo-Replicated, Transactional Datastore

#9

Post by jc_dntn » Fri, May 30, 2014, 6:29 PM UTC

taternuts wrote: post #4

limsup wrote: post #2

I assume it's called this because a cockroach can supposedly survive a nuclear attack. But it's a bad name. It does not invoke good feelings.

I have to agree - maybe 'RoachDB' would be better

I prefer "CockDB".

Re: CockroachDB: A Scalable, Geo-Replicated, Transactional Datastore

#10

Post by rb2k_ » Fri, May 30, 2014, 6:33 PM UTC

How would one communicate with this DB?

I'd love to see some API examples.