CouchDB Weekly News, June 8, 2017

Releases in the CouchDB Universe

  • clusterpost-provider 1.5.0 – This is an Hapi plugin to Execute jobs in remote computing grids using a REST api.
  • couchit 0.5.0 – Couchit is a database iterator that includes a set of tools to help manage documents in a CouchDB database.
  • ember-cli-couch 0.0.8 – Addon for CouchDB document API.
  • pino-couch 1.0.1 – 🌲 Load pino logs into CouchDB (or Cloudant, for that matter)
  • spicy-action 9.4.1 – Web proxy for CouchDB and others, plus Socket.IO relay
  • sqltomango 1.1.0 – A simple Node.js library that converts Structured Query Language (SQL) into CouchDB Mango / Cloudant Query JSON objects.

PouchDB

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

Stack Overflow:

no public answer 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! – 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!

  • “Like, really. Scream at the top of your lungs and dance naked while you can. Look to your left and look to your right; notice there is no one there. Check your lap for occupants and also your legs (kids cling to any part of your body that they can reach). Right now, you are free.” – 15 Things I Would Tell My 20-Year-Old, Childless Self
  • “There’s a fine art to watching a horror movie. Some people are able to respond to every aspect viscerally—talking the characters through tense scenes, freaking out and standing on the couch when the shit hits the fan—in a way that’s charming. It underlines the film’s quality. Other people don’t seem to get it.” – Good dog ruins horror movie
  • “As someone who’s had anxiety for the better part of her 25 years on this planet, I’m always learning new ways to cope when I’m feeling anxious. Some of the tried-and-true strategies I’ve picked up: Go for a run, call my mom, play my guitar, write in my journal. My latest go-to strategy: watch HGTV. Stressful day at work? That calls for some Flip or Flop.” – HGTV Is so Relaxing, It Actually Helps My Anxiety
  • “Is today going to be another day filled with little annoyances? Not if we can help. Here are some expert-approved tips to decompress.” –17 exceptionally easy ways to relax — from people who know how to chill

… and 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 Developer Profile: Joan Touzet

 If you’re following the Apache CouchDB dev mailing list, then you’ve probably been seeing a lot of updates about testing recently. At the forefront of that effort is Joan Touzet. Joan is a long-time committer and PMC member for Apache CouchDB, as well as the point of contact for the CouchDB Code of Conduct. Both getting people excited about using CouchDB and making it easier for them to use it are two aspects of the project that Joan is very enthusiastic about seeing through.

Joan recently offered us some insights into the CouchDB project from her perspective.

Do you want to talk about your background, or how you got involved in CouchDB?

A fellow graduate student introduced me to CouchDB while I was working on systems for student work support and analysis. We used it to extract things students posted on class forum software and then ran various analysis over it, like latent semantic analysis.

I started using the replication feature early on to sync data between multiple servers and my workstation, which was super easy!

I started working at Cloudant shortly after that – I was employee #20 and did a number of things, like devops, development, support and field work. I left Cloudant about a year after they were bought out by IBM.

What areas of the project do you currently work on?

Since returning to active work on the project a few months ago, I’ve been focused on testing, packaging and project management work.

Our test suite has two parts: unit tests written in the Erlang eunit framework, and integration/API tests written in JavaScript. We run these tests regularly in two continuous integration systems: Travis and Jenkins. I’ve been following up on some intermittent failures in these tests.

Packaging is something that got left behind for our 2.0 release, but only in the interest of time. With community sponsorship, I’ve been able to release beta Debian, Ubuntu, CentOS and Windows packages for 2.0. I’m working now to automate this process so that packages can be built with each successful run of our test suite for our major release branches as well as the master branch.

In the future, I hope to extend this to other CouchDB community contributions, such as Cloudant’s full-text and geo search open source addons. Reducing the amount of effort it takes for us to put new releases out the door, and for people to use those releases, is a passion of mine.

What’s a recent development of the project that you’re exited about?

CouchDB was one of the first Apache projects to use git. We’re also now one of the first projects to leverage GitHub more actively than before, beta testing a new integration provided by the Apache Software Foundation’s infrastructure team.

The new integration allows us to manage pull requests and issues directly on GitHub, rather than separately through the traditional JIRA setup. I’ve been spearheading the effort to move onto GitHub issues. We finally went ‘live’ with it about 2 weeks ago.

On a daily basis I triage and curate filed issues. I’m really excited about how much easier this will make it for community members to interact with the developers!

What would you say are the top three benefits of using CouchDB as a database solution?

  1. Sync. It’s the “killer feature” of CouchDB. Whether you’re doing offline-first client development, running a clustered database or distributing data between various server installations, CouchDB’s master-master replication is better than anything I’ve ever used. It Just Works(tm).
  2. Ease-of-use. Every programming language has an HTTP library, and almost all have a JSON library, too. That’s all you need to be successful with CouchDB. Sure, there are language-specific CouchDB client libraries, but in general I don’t find them necessary. It’s just so easy to get going with CouchDB.
  3. Powerful and versatile secondary indexing capabilities. Yeah, it’s a mouthful, but you can do all sorts of interesting things. For simple indexing, we have the Mango library in 2.0. If you want to get more complex, you can write a JavaScript Map/Reduce function. And there are open source addons for full-text search and robust geo indexing, too. I’ve yet to find a kind of indexing that I’ve been unable to do with all these tools at my disposal.

What do you look forward to in the future of CouchDB?

The CouchDB PMC has put together a wishlist for the next few years of CouchDB that includes some great new features relating to our clustering ability (making it easier to scale and administrate), improving Mango’s support for additional search types (“joins”, reduces, bitwise operations, document validation), pluggable storage engines, selective sync, and a “mobile first” replication protocol leveraging HTTP/2.

We even have some ideas to make it easier to contribute to CouchDB, such as figuring out how we could support Elixir plugins. The future is very bright!

What advice do you have for someone who just discovered CouchDB?

  1. If you know SQL, don’t approach CouchDB like a database that you know. Step back from your “5 normal forms” and start afresh. Check out some of the community frameworks around CouchDB (like Hoodie), that make it easy to write applications.
  2. Hang out in our Slack or IRC channels to ask questions.
  3. Don’t be afraid to get your feet wet!

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

Have a suggestion on what you’d like to hear about next on the CouchDB blog? Email us!