Daily Archives: June 18, 2015

CouchDB Weekly News, June 18, 2015

Major Discussions

2.0 progress (see thread)

A list of missing features and suggestions. Feedback is very welcome.

CouchDB questions (or why use a document-based database) (see thread)

A new user to CouchDB wants to make a desktop app that syncs with a Django app and wants to know how a NoSQL, schema-less and document-based database like CouchDB, as opposed to a relational one like PostgreSQL, is to be used to sync the data and include an undo functionality to reverse transactions.

Since transactions are not reversible, it was suggested to use PouchDB with NW.js., implement an undo-feature and recover previous document versions. Also it is being stated that replication and scalability is not as simple in PostgreSQL, whereas with CouchDB, master-master simplicity is a core feature. The main advantage of a NoSQL-database in this case would be, that it’s schema-less and therefore more sustainable.

HTTPS Reverse Proxy Replication (see thread)

A user has been trying to get CouchDB continuous replication to work with a remote database behind an https reverse proxy. It was suggested to check X-Forwarded-Proto.

CouchDB for Android (see thread)

One way to use CouchDB in an Android environment is to start building an Android app that works in sync with CouchDB. Instead of using CouchDB 1.2-beta that was build for Android, it was suggested to use Couchbase Lite, which is also compatible with CouchDB.

CouchDB utc_id behavior (see thread)

Another user recognised uncommon behaviour of new document IDs when being synched between two CouchDB servers that had their clocks synchronised via ntp. While using timestamps to order the documents, they were not in a chronological order, even though OS clocks were in sync…

Releases in the CouchDB Universe

Releases in the PouchDB Universe

Opinions and other News in the CouchDB Universe

Use Cases, Questions and Answers

Stack Overflow:

  • CouchDB override a base JSON document. Question: A standard strategy (or best-practice) for creating a JSON document that a) is based on another document and b) contains a small number of JSON properties that represent overrides to the original document? Answer: It depends on the use case whether to use a CouchDB _list, an approach based on CouchDB _view, or an CouchDB _update handler, and create a view to return each updated document if any overrides exist and the normal document if overrides don’t exist for it.
  • CouchDB – Why is my reduce is always coming as false? Answer: You got the sum of values per title, while you wanted the sum of values in general, by changing the grouping drop-down list to none. Check CouchDB’s wiki for more details on grouping.
  • Indexing names in JSON using elasticsearch in couchdb – trying to implement full-text query for JSON documents. How to index only the title field? Answer: With the elasticsearch-river-couchdb plugin, one can configure the river with a script to remove all fields but the ones to specify. Find an example in the official documentation of the plugin.

no public answer yet (Stack Overflow):

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

PouchDB Questions and Answers

Stack Overflow:

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! – www@couchdb.apache.org
  • 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 l10n@couchdb.apache.org or ping Andy Wenk (awenkhh on IRC).

We’d be happy to welcome you on board!

Events

Job opportunities for people with CouchDB skills

Time to relax!

  • “We could choose to spend extraordinary amounts of money and countless man-hours laboring over a system which provides the reliability we want. We could construct a data center. We could deploy big, expensive machines. We could install redundant fiber and switches. We could drudge over infallible code. Or we could stop, think for a moment, and realize maybe [saying] “sorry” is a more effective alternative.” – Distributed Systems Are a UX Problem
  • “It is obvious that his comments were sexist, but few people could recognise the names or faces of the women he has so thoughtlessly brushed aside. Even in his inadequate apology, he neglected to mention any women scientists who have impressed him during his career…” – The Unseen Women Scientists Behind Hunt’s Nobel Price
  • “Do you feel in the zone working solo plugging away at what you love? Great, make space for that to occur and guard that time like your dreams depend on it — because they do.” – There Are No Hacks To A Meaningful Life
  • “Open Source has a serious problem with sustainability and people working on OS projects for months or years and then giving up on them because they simply don’t want to put any more time in them because it’s so frustrating. So I wanted to have this discussion about what you can do to minimise this frustration.” – The Changelog  #159: Sustaining Open Source Software with Mike Perham
  • “Digging through the company’s membership data, LinkedIn found that software engineering teams in industries outside of technology tended to have many more women.” – This study suggests Silicon Valley really is biased against women
  • “Don’t hire a junior developer as a marketing effort or PR stunt. This reason only considers your company’s best interests rather than those of the candidate. If you’re doing this, you probably haven’t read anything I mention above or below this paragraph.” – The Catch-22 of Being “Too Junior”
  • “It isn’t enough to just state that you’re being color-blind or gender-blind. You need to explicitly say that you’re looking to build a diverse team. The former can imply that you’re being lazy and maintaining your structural biases, but hope to be surprised and delighted when you find a minority or female candidate who can overcome those biases, whereas the latter is a position of active engagement.” – On Recruiting, Inclusiveness, and Crafting Better Job Descriptions

… and also in the news