Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAD2UGCXckZyAhC9EfnkbD6HtB26_fnoWaP-K3+HW-y-Y0VnPZQ@mail.gmail.com>
References: <0D8EFEF0-4701-45CA-9A03-D5659BBD449E@me.com>
 <CAOhG5KmBv76kFH6Z_12xOTBz36JCEYpRtnJcX6hzc1ap0qrEOg@mail.gmail.com>
 <CAD2UGCXckZyAhC9EfnkbD6HtB26_fnoWaP-K3+HW-y-Y0VnPZQ@mail.gmail.com>
From: Joel Wallis <joelwallis@gmail.com>
Date: Thu, 1 Oct 2015 17:16:22 -0300
Message-ID: 
 <CAOhG5KnbMgKQ=ih333dgprxUS-iAjOSSa0CiMa3MxDr1Kvdj=Q@mail.gmail.com>
Subject: Re: pouchdb-find and couchdb 2.0
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=001a1139be00ddb1be052110baeb

--001a1139be00ddb1be052110baeb
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

@Dale and @Ying, I'm sorry if my text sounds aggressive, that was really
not what I meant. English is just my second language so I really don't even
have an idea of how bad "pretending to develop" sounds at the given
context. I was just trying to help.

Please ignore my message above.

2015-10-01 15:55 GMT-03:00 Dale Harvey <dale@arandomurl.com>:

> Ying
>
> CouchDB 2.0 has long been in development and is nearing a beta release, I
> wouldnt be switching existing services to it, but for new product
> development, particularly one that needs mango then I would probably
> recommend doing so. Mango is already supported in CouchDB 2.0, pouchdb-fi=
nd
> will transparently switch to using it if you are speaking to CouchDB 2.0
>
> And Joel, this isnt really a suitable mailing list for questioning people=
s
> 'product differentials' particularly in that aggressive way "pretending t=
o
> develop"
>
> Cheers
> Dale
>
>
> On 1 October 2015 at 17:32, Joel Wallis <joelwallis@gmail.com> wrote:
>
> > You are actually describing Cloudant as the service you are pretending =
to
> > develop. Do you have any planned diferential for this? (Just asking, as
> > product manager, to help you plan your product.)
> >
> > And, PouchDB can be used as an interface for a completely remote CouchD=
B
> > database. Is that what you mean with "couch & pouch transparent"? If no=
t,
> > what are the key diferentials for your implementation? (Just asking, as=
 a
> > software developer, to help you plan your implementation.)
> >
> > 2015-10-01 10:34 GMT-03:00 Ying Bian <ybian@me.com>:
> >
> > > Dear couchdb developers and users,
> > >
> > > I=E2=80=99m new to couchdb & pouchdb and I=E2=80=99m looking forward =
to some comments
> to
> > > the following problem:
> > >
> > > I want to setup a couchdb service in the cloud and provide an SDK to =
my
> > > users for them to use in their apps. They can also use pouchdb as a
> local
> > > replication of their data. An important part of the SDK is the query
> > > interface. I want it to be developer-friendly as much as possible. Th=
e
> > > map/reduce API is too complex for developers with no similar
> experience.
> > > After some investigation, I think maybe [pouchdb-find](
> > > https://github.com/nolanlawson/pouchdb-find <
> > > https://github.com/nolanlawson/pouchdb-find>) is worth to try. Its
> > > mongodb like query language is more intuitive in my mind.
> > >
> > > My questions are:
> > >
> > > 1. Pouchdb-find is still in beta and its documents says "This API is
> > > modeled after the Cloudant query API <
> > > https://docs.cloudant.com/api/cloudant-query.html>, soon to be merged
> > > into CouchDB 2.0.=E2=80=9D  Is the support already merged into couchd=
b 2.0?
> > What=E2=80=99s
> > > the delivery plan for couchdb 2.0? Is it to safe to switch to 2.0 now=
?
> > >
> > > 2. I want the query interface to be =E2=80=9Ccouch & pouch=E2=80=9D t=
ransparent: the
> same
> > > query API would be used for both local pouchdb and remote couchdb. I
> > > suppose this is not a problem. Am I right?
> > >
> > > Any comments would be much appreciated.
> > >
> > > -Ying
> >
> >
> >
> >
> > --
> > Joel Wallis Juc=C3=A1
> > joelwallis.com
> >
>


--=20
Joel Wallis Juc=C3=A1
joelwallis.com

--001a1139be00ddb1be052110baeb--