mc_, you mentioned cockroachdb a couple years back. You ever play with that?

hmmhesays: yeah, just prototypes and local installs

haven't really stretched the distributed part yet

we have some postgres-related work for call center stuff

that i'm hoping becomes the basis for migrating over to a postgres db instead of couch

mc_, I'm working on that now myself.

mc_ postgres instead of couch---you mean for Kazoo??

right now we're cloning couchdocs into postgres but the ultimate goal is to have some middleware to translate the couch views

For what purpose? What benefits does PG offer over Couch with regards to Kazoo?

ruel: ad-hoc queries, mostly

Well i can see that would be a benefit I guess. Couch does have mango query though.

ruel: its not a for sure thing but it is something we're looking into

but i want to get clusters onto couch3 first and see what effect that has

and whether we can create a replication scheme like hmmhesays is talking about for customers that want more querying power

but have them host it or provide it as a ancillary product

couch is absolute trash for any type of large scale analytics

postgres json(b) handling is great and it's pretty simple to do a poor mans master-master with pglogical

ah yes I can see for analytics purposes how that Couch isn't the best lol. Pretty much everything has to be done server side.

Not server side I meant application side. Everything has to be processed in the app after querying pretty much.

Having a bolt-on option sounds good.

I've been running Couch3 for a couple years now. Not on a large scale but I always use it as default, and have set several customers up with it as well.

I use HAProxy to do a few redirects from the 5986 admin port to the proper paths on 5984. Haven't had any issues.

I wrote my own proxy and replicator for couch to make it manageable and and a precursor to getting everything into postgres