couchdb-marketing mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Broberg <>
Subject Re: Draft of Cloudant paper, CouchDB inclusion?
Date Fri, 30 Jan 2015 13:06:57 GMT
Hi, Sebastian and Johs-- Thank you for your comments! I took them to heart
and made some additions to the paper, toward the end of the document. They
are highlighted in the attachment.

I think they are nice improvements, but please let me know if something is
misrepresented and needs correction.

At this point, I'm going to take the cue that this draft is good to go
(especially wrt compliance). We
still have to lay out the document in various formats, so we can always
take copy edits as-needed.

Thanks again! --Mike
Mike Broberg | IBM Cloudant | 200 State Street, Boston, MA 02109 | | (617) 299-1409 Google Voice
(See attached file: whitepaper_managedLocalCouchDB_v5-hlite.pdf)

From:	Sebastian Rothbucher <>
To:	"" <>
Date:	01/29/2015 04:10 PM
Subject:	Re: Draft of Cloudant paper, CouchDB inclusion?


I'm with Johs: one could point out that one can easily SWITCH between Couch
4 free, a fully commercial-backed Cloudant local and the cloud option as
such. You can upgrade and you can also downgrade when you want to leave the
cloud for some reason. Try that with!
By the way: this also improves CouchDB's position as there is a
commercially supported counterpart out - so great on another front also

So thanks for summarizing these things!

On Wed, Jan 28, 2015 at 9:37 AM, Johs Ensby <> wrote:

> Mike,
> Nice paper!  It provides the kind of orientation that is essential to
> development strategy and deployment planning. The fact that it comes from
> major commercial player is a much needed reference on top of the usual
> blog/twitter/youtube/Stackoverflow/Quora scanning to QC the
> not-always-update online docs.
> Two comments:
> I would have expected a few more sentences promoting Cloudant sync (to
> qualify for mobile use is essential these days)
> Mentioning might be a good idea when addressing PouchDB, and as
> there is a compatibility issue there at the moment when it comes to the
> user database api between CouchDB and Cloudant (see
> I think the Hoodie initiative
> deserves a mention since it ties together your “additional replication
> endponts” issue with the node.js world and makes the offline vision a
> practical reality
> A final comment as a Cloudant fan (since i met with the team in Boston in
> 2009)
> You paper title is:
> Deciding Between Cloudant Managed Service, Cloudant Local, and Apache
> CouchDB™
> .. and one of your best arguments is that you DON’T need to decide
> Cloudant and A-CouchDB.
> Isn’t that a good point emphasize in the conclusion of the paper?
> johs:)
> > On 27 Jan 2015, at 17:48, Mike Broberg <> wrote:
> >
> > Hello, marketing community-- I'm working on a short paper that outlines
> the differences between Cloudant's various services, and would like to
> include Apache CouchDB alongside them as an option.
> >
> > A draft of the copy is available for comments at

> <
> I also included a potential layout of the document (attached) so you can
> see how the images might look. (Disclaimer: I am not a graphic designer.)
> >
> > A couple notes:
> >
> > I wasn't sure how to handle PouchDB. I lumped it in with the ASF
> trademarks statement in the draft, but I'm not sure if it applies. So I'm
> copying the ASF trademarks team here on that. Or, maybe this is a
> for Dale, Nolan, etc.?
> > Also, I wrote this draft with an eye on the near future, anticipating
> clustering in Apache CouchDB.
> >
> > Ideally, I'd like to consolidate feedback from the community by the end
> of this week. Please let me know if you anticipate needing more time.
> you! --Mike
> > --
> > Mike Broberg | IBM Cloudant | 200 State Street, Boston, MA 02109 |
> | (617) 299-1409 Google Voice
> > --
> > (See attached file: whitepaper_managedLocalCouchDB_v4.pdf)
  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message