Comments on: Unconventional architectures that might scale (I)

By: Wordpress & Couchdb and Ruby « log4p

Wordpress & Couchdb and Ruby « log4p — Thu, 28 May 2009 12:15:29 +0000

[...] This might not seem very useful, and when only receiving data from WordPress it isn’t. In the future other applications would also publish content to the same [...]

By: CouchDB - Slacker database in Erlang | Finalist Developers Blog

CouchDB - Slacker database in Erlang | Finalist Developers Blog — Mon, 06 Apr 2009 09:17:16 +0000

[...] databases weer helemaal hot. Een aantal prototypes voor de architectuur die ik momenteel ontwerp zijn ook gebaseerd op het gebruik van een dergelijke database. Een goed moment om er eens een [...]

By: Remco

Remco — Sat, 28 Mar 2009 12:00:20 +0000

The Book Of JOSH ??

By: peter

peter — Thu, 26 Mar 2009 22:46:36 +0000

@Giogio I’m not sure what you are actually asking… which master part, and what reading?

By: Giorgio Sironi

Giorgio Sironi — Thu, 26 Mar 2009 22:32:16 +0000

Maybe ignoring the writing is oversimplifying, I was wondering ‘How he will do the master part?’ while reading…

By: Nils Breunese

Nils Breunese — Tue, 24 Mar 2009 08:51:47 +0000

I hear Varnish is a great HTTP accelerator to put on top of CouchDB: http://varnish.projects.linpro.no/

Also of interest might be CouchDB’s show and list functions, which convert documents and views into non-JSON formats, if you’d like that: http://wiki.apache.org/couchdb/Formatting_with_Show_and_List Looks pretty awesome.

By: peter

peter — Tue, 24 Mar 2009 06:09:27 +0000

Well 'ideal' is a big word, but yes I think it would be worthwhile to work through those operations. Lucene based frameworks like Compass keep their Lucene indexes up-to-date in that fashion. But you will probable need some sort of mapping strategy to decouple changes to your model from changes to the document model in CouchDB.

By: Chad

Chad — Tue, 24 Mar 2009 02:20:55 +0000

Nice work – The architecture approach seems valid. Like you say, read optimized, but with some additions could scale and perform well. I’ve been looking for thoughts on grails fronting a couchdb repository for some of these same reasons. And your groovy service and this comment was of interest to me.

>> I added a simple service to Groovy which facilitates writing/updating entities to CouchDB via the REST interface (It would probably be better to use Hibernates’ interceptors to do this, doens’t change the PoC though)

Do you mean it would be ideal to work through the hibernate .save, .delete operations with some type of couchdb directive on the grails domain objects that are to be saved to the couchdb?

thanks,
chad.