Hi there,

I've copy and pasted a draft for the community's review. Let me know if you'd like me to share this as a Google doc if that's easier.

The submission date is 12/4. Once there's agreement on responses and who will be the spokesperson, let me know if you'd like me to loop back in with Cassandra, the writer at Software Magazine, on behalf of the community.


Name and title of person responding to these questions (as you would like it to appear in the article).
[TBD by CouchDB Community]

Please list your firm’s DBMS offering(s) and database model(s), as well as what sets it (them) apart from other DBMS solution(s).
Apache CouchDB™ is an open source NoSQL database that moves data through a unique model of replication and synchronization. CouchDB allows data to be distributed across multiple data centers and devices—whether they’re on-premises or across the globe—bringing application data to users wherever they need it. The database well-suited for high-traffic applications that use lots of reads and writes, and CouchDB’s replication and synchronization allows for continuous use: even when devices are offline, “always on” applications can withstand network problems and maintain uptime.

Specific to “Big Data,” please discuss the benefits of this particular type of DBMS model (if you offer multiple types, please comment on each). What are the limitations?
CouchDB stores data as JSON documents, rather than in structured tables like relational databases. This approach lends itself to a more denormalized data model, where all the data related to a particular record is encapsulated in a single document. Because data in CouchDB can be logically grouped together into individual documents, CouchDB implementations provide the ability to shard the database for better performance and scale horizontally across many nodes.

At the heart of CouchDB’s distributed system design is peer-to-peer “masterless” data replication. The same mechanisms that allow CouchDB to create readable and writable database replicas within a single cluster allow it to move and synchronize data between clusters around the world or directly with Web browsers and mobile applications. As applications grow, so does the amount users are interacting with and creating data, which is why a database that moves data and scales gracefully is critical.

There are limitations for highly relational workloads that don’t benefit from the flexible schema of CouchDB, or for applications that rely on databases to support transactions or prioritize hard consistency over high availability.

Specific to Big Data, is there a benefit to an open source versus commercial solution, and vice versa? Why or why not?
As businesses turn to DBMS solutions to handle a wide array of projects, the open source options offer free, customizable, community tested solutions. Many commercial products are built on open source databases, so companies have the flexibility of the open source software coupled with the services and benefits of a brand (for example, IBM Cloudant offers a CouchDB-based managed service, with additional features Cloudant has built and layered on top of the CouchDB open source database). Another benefit, and a reason behind the open source basis of so many NoSQL databases, is the innovation that inherently accompanies open source. Instead of a small team working on a proprietary solution, open source projects are supported by communities with diverse collaborators from different backgrounds.

What trends can we expect in the near future in terms of DBMS as more organizations look to add or enhance big data to their business strategy?
Ensuring high availability of applications is increasingly important, so we expect to see organizations’ adopt strategies for moving data between data centers and devices to make applications highly available. Enterprises are adopting “offline first” design principles for Web and mobile apps; organizations need to have the flexibility to move their data to locations both locally and around the world, and the ability to enable app usage regardless of network connectivity.

Artwork: Please provide any images (screen shots), diagrams, illustrations, and infographs, that help visualize your solution. Images should be sized to 300 dpi, or larger if the resolution is lower.

Lynnette Nolan
Marketing Communications & PR Specialist
Cloudant, an IBM Company

Mobile: (781)775-0579
Find me on:
200 State St
Boston, MA 02109
United States

Inactive hide details for Noah Slater ---12/01/2014 12:36:09 PM---Oh, thanks for picking this up Lynnette! Happy to review any Noah Slater ---12/01/2014 12:36:09 PM---Oh, thanks for picking this up Lynnette! Happy to review any draft you produce!

From: Noah Slater <nslater@apache.org>
To: Sally Khudairi <sk@apache.org>
Cc: Lynnette Nolan/Cambridge/IBM@IBMUS, "marketing@couchdb.apache.org" <marketing@couchdb.apache.org>, "andy@nms.de" <andy@nms.de>, "jan@apache.org" <jan@apache.org>, "nslater@apache.org" <nslater@apache.org>
Date: 12/01/2014 12:36 PM
Subject: Re: Software Magazine article on DBMS

Oh, thanks for picking this up Lynnette! Happy to review any draft you produce!

On 21 November 2014 at 20:45, Sally Khudairi <sk@apache.org> wrote:

Noah Slater