Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of bchesneau@gmail.com
 designates 209.85.223.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <629F0E3A-6192-4555-90C9-379DA39E0161@dionne-associates.com>
References: <40BCC84F-C695-492E-B56E-08C60955A3D8@apache.org>
	<CAHdjipK3UOg3FbnA_sGUpcP8YXOa0PYfnn3Zx0JmTodPjJdu+A@mail.gmail.com>
	<CABvT1DFAcMQtx4WGBPwZwqRkNzVBFPCnFb_djirDtS_9RFJsFw@mail.gmail.com>
	<3B2D6B8E471743B49554B23F98B8414C@cloudant.com>
	<629F0E3A-6192-4555-90C9-379DA39E0161@dionne-associates.com>
Date: Thu, 1 Nov 2012 11:17:05 +0100
Message-ID: 
 <CAJNb-9rjTchKgj9CGPQj0Jjqfa4sWj4uXme_zDz+h-MrzFdfFA@mail.gmail.com>
Subject: Re: CouchDB Plugins First Draft
From: Benoit Chesneau <bchesneau@gmail.com>
To: "dev@couchdb.apache.org" <dev@couchdb.apache.org>
Content-Type: multipart/alternative; boundary=bcaec529a0b130020004cd6c5291

--bcaec529a0b130020004cd6c5291
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

there are also other plugins around :

https://github.com/benoitc/couch_randomdoc

https://github.com/benoitc/couch_zmq wich is using erlzmq

https://github.com/benoitc/couch_es

https://github.com/refuge/bigcouch_spatial

https://github.com/refuge/couch_dbupdates

https://github.com/ocastalabs/CouchDB-XO_Auth

....


So on erlang the situation is quite complex. As a free reminder when we
spoke about rabbitmq plugins in january, nobody wanted that which let me
perplex. Like I said do we we want a plugin system or just a way to load
app?

About couchdb-lucene for example it could be rewritten to use more of the
internals of couchdb. And probably using jinterface instead of living
externally so it could be better integrated.  (This is just an example of
what could be done) . couch_es could be fully written in elixir or js and
distributed as an internal couchapp. Same for random doc etc .

Imo when we speak about plugins we should have in mind the of their
deployement. This is one thing to install a plugin on a machine , another
to make sure that this plugin is installed on others machines. And when I
say other machines I'm not only speaking about machines in your lan (some
of us have tools and people for that) but machines of remote possibly
stranger people replicating your data . ANd this part is definitely not
possible easily with something like rabbitmq plugins.


- beno=EEt


On Thu, Nov 1, 2012 at 11:01 AM, Bob Dionne <dionne@dionne-associates.com>w=
rote:

> Reminds me of my favorite book - "Sketches of an Elephant"
>
> Jan, thanks for putting a stake in the ground, I've wanted to see this
> forever. The proposal in my mind takes too much of a product management o=
r
> marketing view (perhaps knowingly). Here's how it will look the buttons o=
ne
> will push, etc..
>
> I think the "what" and "how it works" are important to decide on first,
> .eg. @rnewson's suggestion for something like RabbitMQ. Reading the docs
> for that, the "what" is much clearer.
>
> Looking over the efforts to date, couchdb-lucene, and geocouch, these two
> are quite different in terms of design, one is roughly loosely coupled, t=
he
> other more native (in the same VM). A plugin architecture, in my mind,
> should emerge from the code refactoring and layout we're currently
> discussing. We should ask and answer questions such as:
>
> 1. the role of externals
>
> 2 access to the storage layer (API?)
>
> 3. separation from http layer
>
> 4. support for code upgrades
>
> 5. balancing of resources
>
> I didn't mention Auth and Logging as I think these are separate in terms
> of concerns, more system oriented. Whereas geocouch and couchdb-lucene ar=
e
> actually extending the functionality in meaningful ways.
>
>
> On Nov 1, 2012, at 5:30 AM, Simon Metson <simon@cloudant.com> wrote:
>
> > +1 - keep it simple for the first iteration.
> >
> >
> > On Wednesday, 31 October 2012 at 23:40, Robert Newson wrote:
> >
> >> I quite like the rabbitmq approach (a lot like the apache httpd
> approach).
> >> you can enable/disable/list plugins but the tool doesn't include the
> >> downloading and managed repository bits, which is a huge rabbit hole
> (pun
> >> intended).
> >
> >
> >
>
>

--bcaec529a0b130020004cd6c5291--