We are using the mochijson2 (Mochiweb) module decode and encode functions to convert the data in and out.
The module is optimized and the json data is decoded into a structure where keys and values are binaries.

In order to ease the use of this structure I’ve developed some useful functions like the usual set_, get_ and delete_value(Path, Struct) but also extend(S, Structs) and withdraw(S, Structs).
Those two, respectively, extend(update + add) or withdraw(delete key pairs) one structure with one or more other(s), returning a new modified struct.

@Luis

Great to ear from you Luis

Indeed, the Web is moving, waving, swelling, exploding, erupting, … it’s alive.

(speak to you really soon)

Hughes: this is really cool! (Let’s have some beers some day to discuss more about SciTE and great rare movies!)

Greetings from Valencia!

Luis

That being said, Couch didn’t work for me because of the filtering that I needed done. Currently, it’s difficult to have dynamic queries sent to Couch and have its views handle them efficiently. Mnesia is proving to be a bit more adept at this task. Couch is perfect for the amorphous data that needs to be stored, though, so I’m torn… Probably staying with Mnesia for now, with one eye still on CouchDB.

Mochiweb behind Nginx indeed kicks ass. It’s scary fast.

What json lib are you using? There’s one I found in ecouch that’s kind of a pain, but the strings are in binary, which is nice.

I will take a look at Pure, but Dojo with Django-like templates is working now.

Good luck, guys. Sounds like you’re on a great path.

Cheers,
BA

We had a close look at CouchDB a few months ago. The project seemed really appealing but was only at an early alpha stage at that time.

The API is entirely based on http REST (which is a good idea, IMO), but when using Erlang, having the possibility to natively speak with Mnesia (structure) is a real plus.

We have thought our model with care and ended up with a kind of ‘hybrid’ relational-document architecture. Anyway, we’ll still keep a eye on CouchDB.

@Abhijith

Regarding Erlyweb, to be honest, I didn’t really try it. The explanation is simple : I was not looking for a full features framework à la Rails-Django.

In Ruby I would certainly have chosen Merb, probably Webpy in Python, and in Erlang I found the Mochiweb toolset really handy to start with a simple and efficient app server.

Here is a brief extract of our decision-making process – We consider that the client browser has an active role to play in a distributed system (… did I mention Google Chrome ? …) : in our case, to be entirely responsible for the ‘View’ part of the app. The direct consequence : we don’t need (99%) to transform HTML at server level and thus we can eliminate this requirement of our list when looking for a solution. -

Having said that, I’m sure Erlyweb has a lot to offer when it comes to web development and represents a solid alternative to Rails and Co.