CouchDB Developer Profile: Nick Vatamaniuc

Nick Vatamaniuc is a Virginia-based software engineer at Cloudant and an Apache CouchDB committer. If his name sounds familiar, you might remember the post he wrote for our series “The Road to CouchDB 2.0” last year on the newly updated Replication feature.

Almost a year later, Nick shares some of his insights on CouchDB, Erlang, the latest updates to replication in 2.0, and where CouchDB is headed in the future.

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

I discovered CouchDB around 2010 while looking for a replacement for an existing database. CouchDB had won over all the other alternatives because of its durability, master-to-master replication, and a built-in easy to use web interface to query and inspect data.

But technical merits are only half the equation. I was also impressed with the Apache CouchDB community. They were very welcoming, friendly, and knowledgeable. Always willing to listen and help.

For the next 5+ years I was a CouchDB user and designed it at the core of a few products. During that time it ended up on thousands of servers across the planet, some in harsh and isolated environments. There wasn’t a single instance where CouchDB lost a customer’s data.

Another thing that made CouchDB stand out was that it was written in Erlang. For me it was a new language, so I looked it up and liked what I found. It made it easy to build distributed and fault tolerant systems. So I started to learn it in my spare time.

In 2015 I started working at IBM Cloudant, and last year got elected as an Apache CouchDB committer. Currently, I enjoy contributing to the Apache CouchDB project and being part of the CouchDB community.

What areas of the project do you work on?

I work mainly on what CouchDB developers call “DB Core”. It includes things like data storage, clustering, replication and HTTP layer.

Recently I was involved in improving the replicator. We had just merged to master an updated replicator which can handle a much larger number replication jobs and has a simplified replication task monitoring API.

What’s a recent development/event/aspect of the project that you’re excited about?

Refactoring the project to use less source repositories. Previously most of the core applications were in separate source repositories. Now they are in a single repository and so it is easier to contribute, track changes and build the project from source.

What do you think are the top three benefits of using CouchDB as a database solution?

Master-to-master Replication: Few databases support this feature. It allows creating custom clustering topologies (a ring, star, or a tree for example) with various availability and scalability trade-offs.

Durability and Fault Tolerance: CouchDB 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. This is a simple and robust design. Also because it is written in Erlang, with its famous fault tolerance capabilities, if some parts of the database crash they automatically restart while the rest of the database core stays up and serves client requests.

Built-In Web Interface: Being able to open Fauxton and inspect, query and modify data is a very powerful and useful feature. I can speed up product development, for example by letting a front end developer populate the database by hand with some “mock” data with a few mouse clicks so they can refine their design. It can also help in production when something is not working quite right and there is a need to see the state in the database. For newcomers it makes it easy to learn and experiment.

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

One of the most interesting new developments I think is the Pluggable Storage Engines work done by Paul Davis. It would allow creating custom data storage backends with various trade-offs and characteristics.

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

Open Fauxton and experiment! Add some data, and then write some code to modify the data. Have some fun.

Find us on Slack or IRC. Ask questions.

Learn about _bulk_docs API endpoint to insert multiple documents at the same time. That is often a good way to improve insert performance.

Learn about change feeds and use them to create more responsive and dynamic applications.


For more about CouchDB visit 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!

5 thoughts on “CouchDB Developer Profile: Nick Vatamaniuc

  1. CouchDB as a Database Solution – Part 2 – CouchDB Blog

  2. CouchDB as a Database Solution – Part 3 – CouchDB Blog

  3. Developer Advice for CouchDB Newcomers, Part 1 – CouchDB Blog

  4. Open Source Your Summer! – CouchDB Blog

  5. Developer Advice for CouchDB Newcomers – Part 2 – CouchDB Blog

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s