Couchdb Interview Questions

MongoDB and CouchDB are traditionally open sources No SQL, document-oriented database.   Apart from storing the data outside, they have nothing in common. Even their interface storage and replication methods are different in each and every approach.

CouchDB is simple and easy to maintain no additional cost or efforts are given by the user to maintain this Database. It is flexible and has more scalability, which makes it a better product among others.

Based on the requirements and assumptions in the project a particular kind of database is chosen. CouchDB offers few out of the box features and this leads to the high demand of this database irrespective of challenges. Discussing the replication, multi-master replication seems attractive to the clients in the context of using this database in their project.

Still, the challenge remains in replication is conflict resolution. Maintenance of this database is quite simple and affordable. It doesn’t require too much caring and attention. This is considered as one of the most stable and user-friendly DB and crashes only in critical situations. But it is not always possible to save and protect the whole data after a crash, sometimes data can be lost forever if the proper process not followed. One of the other advantages is as it only uses JSON and HTTP, it reduces the use of middle server and cut downs the cost and is used directly from browser JavaScript.

Best example, which can be given here, is when the user does not wish to change the document data too frequently and without this can define all possible queries in advance.  Apart from these services the CouchBase server can fulfill several other requirements like SQL integration, scale-out architecture, core database engine etc. 

• It can be used directly to write a client’s application without the use of any other server reducing the development time.
• It helps to replicate the database of client and the filter feature helps to replicate the database of the specific user.

• JSON documents – Each and every data is stored in JSON document.
• RESTful interface- Each and every data task and management can be done via HTTP.
• N-Master replication- Unlimited amount of masters can be used for replication topologies.
• Built for offline – This database can replicate to devices (e.g. Android phones) and can be used in offline mode. But the data will be in sync when the device is back online.
• Replication filters – Filters can be applied to replicate different nodes in the database.

1. Index service
2. Data service
3. Cluster manager component
4. Query service

• The overall storage limits up to 2 gigs per file.
• There is a requirement of validation and fix up of cycle once there is crashes or power hence, for large file fix up time is prohibitive.
• Sometimes Mnesia is not suitable for large-scale database hence it creates a hindrance.

Manual testing uses other testing and seeing the procedure and requires a technical knowledge of SQL and shell scripting. It is a time and efforts consuming procedure and is prone to errors.

1. Data manager
2. Cluster manager