CouchDB Weekly News, December 14, 2017

Releases in the CouchDB Universe


Opinions and other News in the CouchDB Universe

CouchDB Use Cases, Questions and Answers

Stack Overflow:

no public answer yet:

PouchDB Use Cases, Questions and Answers

No public answer on Stack Overflow yet:

For more new questions and answers about CouchDB, see these search results and about PouchDB, see these.

Get involved!

If you want to get into working on CouchDB:

  • We have an infinite number of open contributor positions on CouchDB. Submit a pull request and join the project!
  • Do you want to help us with the work on the new CouchDB website? Get in touch on our new website mailing list and join the website team! –
  • The CouchDB advocate marketing programme is just getting started. Join us in CouchDB’s Advocate Hub!
  • CouchDB has a new wiki. Help us move content from the old to the new one!
  • Can you help with Web Design, Development or UX for our Admin Console? No Erlang skills required! – Get in touch with us.
  • Do you want to help moving the CouchDB docs translation forward? We’d love to have you in our L10n team! See our current status and languages we’d like to provide CouchDB docs in on this page. If you’d like to help, don’t hesitate to contact the L10n mailing list on or ping Andy Wenk (awenkhh on IRC).

We’d be happy to welcome you on board!

Job opportunities for people with CouchDB skills

Also in the news

Submit news to the CouchDB Weekly

Reach out to us with your news suggestions by sending us an email or by contacting us on Twitter @CouchDB.

CouchDB as a Database Solution – Part 3

It may be the case that you missed the other parts of this series where we discussed some of the feedback we’ve received from our developers on the top benefits of using CouchDB as a database solution.

If that’s the case, we encourage you to take a minute to venture back. In part one we discussed sync and replication. Part two followed with a discussion of CouchDB’s built-in web interface and its versatile secondary indexing capabilities.

In addition to the aforementioned features, our interviews uncovered other favored CouchDB features such as its application data model consistency, its support for clustering, and its schema flexibility.

Paul Davis spoke to application data model consistency saying that most people think of this as replication but one of the things that he’s always liked about CouchDB is how an application can reuse the same data model regardless of programming language or deployment environment. He also added that no schema was a top benefit. He shared that the relational model is great for relational data, but not all structured data fits that model.

Developer Garren Smith mentioned that he liked the fact that CouchDB is a proven technology, and a database you can trust. He also spoke to the benefit of version 2’s support for clustering, stating that it is a lot more fault-tolerant.

In speaking of fault tolerance, Nick Vatamaniuc stated that CouchDB’s simple and robust design is resilient in the face of crashes and power failures. Data is always appended to the end of database files and never directly re-written. Nick shared that because it is written in Erlang, if some parts of the database crash they automatically restart, while the rest of the database core stays up and serves client requests.

To swing things back to Paul, his third top benefit was the declaration that Erlang is a wonderful language for operations, stating that the ability to open up a shell on a node that’s misbehaving to diagnose bugs and misbehaviors is invaluable.

Another thing that’s invaluable is the contributions made by the CouchDB developers.

We look forward to sharing more of what we’ve learned through our interviews and will continue sharing their insights with the CouchDB readers. Next up, we will discuss some developer advice to those new to the platform as well as some specifics on the future of CouchDB. Stay tuned!


Stick around to hear more details from our developer interviews and feel free to let us know if there’s something in particular that you’d like to see covered on the CouchDB blog, we would love to accommodate. Email us!

For more about CouchDB visit or follow us on Twitter at @couchdb