I appreciate CouchDB’s many attempts to use universal web formats in everything it does: RESTFUL HTTP methods in every interaction, JSON , javascript > to configure the database and documents.
CouchDB seems to scale very well, but the individual cost to make a request usually makes relational people afraid.
Many small business applications need to deal with just one machine and all that. In this case, talking about scalability does not say too much, we need more performance for each request, or people will not use it.
BERT (the binary term ERlang http://bert-rpc.org/ ) has proven that it will be a faster and lighter format than JSON, and it is native to Erlang, the language CouchDB is written in. Can we capitalize on this using BERT docs instead of JSON?
I'm not just talking about getting in the views, but for everything that CouchDB does, including synchronization. And, as a result, use Erlang functions instead of javascript .
This will change some of the original principles of CouchDB, because today it is very web-oriented. Considering that, in my opinion, few people will make their database API publicly available, and as a rule, users access the data through the application, it would be nice to configure CouchDB to work faster. HTTP + JSON calls can still be handled by CouchDB, given the added cost in these cases due to parsing.
source
share