Live data from Hacker News

CouchDB 3.0

blog.couchdb.org

11–20 of 161 posts

Re: CouchDB 3.0

#11
Oh wow, this is great news. I though the project was effectively long dead. Is there a new/up-to-date "couchapp" too?

> Default installations are now secure and locked down.

More good news!

Anyone have recent experience with couchdb?

I see the (quickstart) docs use plain http - should one terminate ssl in front, eg with a recent version of haproxy?

Re: CouchDB 3.0

#12
At this point why would you use CouchDB over something like MongoDB?

Seriously asking...

Over the past 5 years MongoDB has gotten a great storage engine, transactions, distributed transactions, multi master replication, first class change streams and is very very solid as a foundational piece of infrastructure you can rely on while CouchDB has languished. I can’t imagine reaching for it in my tool belt when I need a document store over MongoDB but I’m obviously biased so I’m wondering if there is a lot I’m missing.

Obviously it’s cool from a more open source databases standpoint — I love learning about how things are built and evolve over time.

Re: CouchDB 3.0

#13
post #11

Oh wow, this is great news. I though the project was effectively long dead. Is there a new/up-to-date "couchapp" too? > Default installations are now secure and locked down. More good news! Anyone have recent experience with couchdb? I see the (quickstart) docs use plain http - should one terminate ssl in front, eg with a recent version of haproxy?

For anyone else looking to quickstart but on Kube, https://operatorhub.io/operator/couchdb-operator. Should add 3.0 soon.

Re: CouchDB 3.0

#14
post #3

Earlier quoted context omitted.

I didn't understand. You mean it's unique to work over http(s)?

I mean your CouchDB instance itself is represented by a host and port and your application's data could be stored there and a native HTTP-based API to access said data . This is contrasted to most where you would need a driver and it's accessible only in the "back-end".

> itself is represented by a host and port and your application's data could be stored there

All databases are represented by a host and a port. I think you mean CouchDB offers a HTTP-based API that allows queries to be run without requiring a database-specific library and that because it's HTTP, it can be accessed via a browser.

Re: CouchDB 3.0

#15

Maybe I'm being petty, but it doesn't fill me with confidence when the ssl certificate on their website isn't even configured properly (valid for uberspace.de domain). To clarify: seems their main site is on apache.org. But, their www.couchdb.org site (hosted on uberspace.de) doesn't have a correct cert.

[deleted]

Re: CouchDB 3.0

#16
post #4

One interesting thing you can do with CouchDB is that you can have a webapp where a user can specify their own database and credentials and it works over HTTP(s). That's pretty unique. I'd love to see a SaaS using CouchDB and their "on-premise" offering just means the user provides their own database. I'm not sure how payment would work though - perhaps some verification proxy? Firebase is the gold-standard for offli…

Cloudant on IBM Cloud is CouchDB API/replication compatible and offers support for Apache CouchDB (1). Also, OpenWhisk integrates nicely with CouchDB/Cloudant and can even be a backing persistence for it (2) (1) https://www.ibm.com/cloud/blog/announcements/announcing-supp... (2) https://github.com/apache/openwhisk/blob/master/tools/db/REA...

Cloudant is awesome, but it's way too expensive IMHO.

Re: CouchDB 3.0

#17

Earlier quoted context omitted.

I mean your CouchDB instance itself is represented by a host and port and your application's data could be stored there and a native HTTP-based API to access said data . This is contrasted to most where you would need a driver and it's accessible only in the "back-end".

> itself is represented by a host and port and your application's data could be stored there All databases are represented by a host and a port. I think you mean CouchDB offers a HTTP-based API that allows queries to be run without requiring a database-specific library and that because it's HTTP, it can be accessed via a browser.

Haha, yes, exactly. I omitted the most important part - the [HTTP-based API].

Re: CouchDB 3.0

#19
post #4

Earlier quoted context omitted.

Cloudant on IBM Cloud is CouchDB API/replication compatible and offers support for Apache CouchDB (1). Also, OpenWhisk integrates nicely with CouchDB/Cloudant and can even be a backing persistence for it (2) (1) https://www.ibm.com/cloud/blog/announcements/announcing-supp... (2) https://github.com/apache/openwhisk/blob/master/tools/db/REA...

Cloudant is awesome, but it's way too expensive IMHO.

Send me an email (in profile.) Would love to chat and see what we can do for you.

Re: CouchDB 3.0

#20
post #11

Oh wow, this is great news. I though the project was effectively long dead. Is there a new/up-to-date "couchapp" too? > Default installations are now secure and locked down. More good news! Anyone have recent experience with couchdb? I see the (quickstart) docs use plain http - should one terminate ssl in front, eg with a recent version of haproxy?

I wish couch was used whenever users ask for an app to "sync to Dropbox". I don't know if this changes with 3.0 but couch is naturally database per user, took me five minutes to install on my rpi with docker, very good admin interface, the database is the frontend (no driver or separate process), and let's the application layer handle conflicts.
Post reply on HN