Couchbase Other Solutions Considered

Chief Information Officer at a tech company with 51-200 employees
We also looked at MongoDB, some sort of eMemory, and cache layered with a traditional relational database for performance sake, because we churn a lot of data. We collect for each customer upwards of around 20GB/hour of data. Therefore, performance is important to us, so NoSQL eventually became the obvious choice. The decision was between this solution and MongoDB. We chose this because it came with N1QL, which is their query language. Whereas MongoDB, at that time, did not come with any sort of query capability. View full review »