Return-Path: X-Original-To: apmail-couchdb-marketing-archive@minotaur.apache.org Delivered-To: apmail-couchdb-marketing-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0456417305 for ; Thu, 29 Jan 2015 21:05:57 +0000 (UTC) Received: (qmail 36645 invoked by uid 500); 29 Jan 2015 21:05:57 -0000 Delivered-To: apmail-couchdb-marketing-archive@couchdb.apache.org Received: (qmail 36605 invoked by uid 500); 29 Jan 2015 21:05:57 -0000 Mailing-List: contact marketing-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: marketing@couchdb.apache.org Delivered-To: mailing list marketing@couchdb.apache.org Received: (qmail 36592 invoked by uid 99); 29 Jan 2015 21:05:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Jan 2015 21:05:56 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sebastianrothbucher@googlemail.com designates 209.85.192.43 as permitted sender) Received: from [209.85.192.43] (HELO mail-qg0-f43.google.com) (209.85.192.43) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Jan 2015 21:05:32 +0000 Received: by mail-qg0-f43.google.com with SMTP id e89so34296106qgf.2 for ; Thu, 29 Jan 2015 13:05:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=n1DOreKCDp9kaJeJFgKRlu0103Ld3A973CoGkCdLI20=; b=buPS6PKx+ptvT2fCc2KY+PP6yTSDuLkZXDMepIHeRKVbb6yTpuvEExea5ZkCPCnMKS lFHWnE4+ZwqTyShINivP8V0RfaiLLygTEQdRWtsj9lRrfeIGt6umG7qANvF/150b9y3v cJZ7JLo2JtZ3YSaQPAy9mT33GHVHaoQCj6ZJgtrRh6aBpTcGnpHcO8hB7l33Xkgpg502 ohaacV703etNPi6MJXD32UGvMMg84DBFTkiPZ7jXovNrqG+qkfS9WEsU83TtuEpPrvBa xIdLqcWcbN0B4Pg0PrS+HcNm76ybqi/wzEG1HqH9wCY+bAHQsSinFuaIddJlq32fsNtn HWWQ== MIME-Version: 1.0 X-Received: by 10.224.72.8 with SMTP id k8mr5551023qaj.26.1422565529832; Thu, 29 Jan 2015 13:05:29 -0800 (PST) Received: by 10.140.194.8 with HTTP; Thu, 29 Jan 2015 13:05:29 -0800 (PST) In-Reply-To: <52AC422E-5500-48B2-9F08-A9DE1A87A156@b2w.com> References: <52AC422E-5500-48B2-9F08-A9DE1A87A156@b2w.com> Date: Thu, 29 Jan 2015 22:05:29 +0100 Message-ID: Subject: Re: Draft of Cloudant paper, CouchDB inclusion? From: Sebastian Rothbucher To: "marketing@couchdb.apache.org" Content-Type: multipart/alternative; boundary=047d7bdca0c013547b050dd0d9b5 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bdca0c013547b050dd0d9b5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, 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 SF.com! 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! Sebastian 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 bot= h > development strategy and deployment planning. The fact that it comes from= a > 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 Hood.ie 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 > https://github.com/hoodiehq/faq/issues/77). I think the Hoodie initiative > deserves a mention since it ties together your =E2=80=9Cadditional replic= ation > endponts=E2=80=9D issue with the node.js world and makes the offline visi= on 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=E2=84=A2 > .. and one of your best arguments is that you DON=E2=80=99T need to decid= e between > Cloudant and A-CouchDB. > Isn=E2=80=99t 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 > https://docs.google.com/document/d/1-t8xRXnMqHYJi2PcxHzX3By3eoZUkWxzKqQg5= K3tLbU/edit?usp=3Dsharing > < > https://docs.google.com/document/d/1-t8xRXnMqHYJi2PcxHzX3By3eoZUkWxzKqQg5= K3tLbU/edit?usp=3Dsharing> > 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 questio= n > 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. Tha= nk > you! --Mike > > -- > > Mike Broberg | IBM Cloudant | 200 State Street, Boston, MA 02109 | > mbroberg@us.ibm.com | (617) 299-1409 Google Voice > > -- > > (See attached file: whitepaper_managedLocalCouchDB_v4.pdf) > > --047d7bdca0c013547b050dd0d9b5--