What is our primary use case?
We are solution providers and we are vendors. We provide products to our clients.
I am working on Couchbase and Elasticsearch together. We use Couchbase as a family data engine for immigration assistance. We use Elasticsearch to replicate the data in realtime from Couchbase, and then we use the search functionality via Elasticsearch.
We are building a property listing system and when it was created we stored all of the data in Couchbase in realtime. We scrape from different sources and select the data from the user agents, and the property agent as well, and then store it. There is a retrieval method built into Couchbase.
What is most valuable?
I have found the views to be very valuable.
When using Couchbase, I did not face any issues and I think it's quite straightforward. The documentation is clear for the tools, the query, and the indexing. These are easily understood.
I have not faced any difficulty when using Couchbase. It may be because I am a senior developer, so it might be a problem for a junior developer, but I cannot say anything about them.
The interface is good, the dashboard is good, and the analytics is very good. These features have helped us a lot.
What needs improvement?
Most of the time, the only issued that I have faced was when we upgraded the Couchbase version. It is very difficult to load the backup of the older version to the newer version.
The only problem with it, I mentioned, the loading data from a different version. For that, we use replication to solve the issue. This is the only bad issue we faced, otherwise it is perfect.
For how long have I used the solution?
I have been using Couchbase for three years.
Currently, I am using version 6.0.
What do I think about the stability of the solution?
It's stable. I have not experienced any issues.
What do I think about the scalability of the solution?
It's a scalable solution.
In our organization, we have two to three people using Couchbase, and another two to three developers are using Elastic Search.
How are customer service and technical support?
Communication with the technical support team is rare because most of the time, our clients have not purchased the enterprise version. We solve the issues on our end to keep the project cost low. The project was not too extensive, so we never needed to contact support.
Which solution did I use previously and why did I switch?
Previously, we were using MongoDB.
How was the initial setup?
The initial setup was straightforward.
We have deployed this solution onto our own cloud. We installed the Agentpoint and deployed Couchbase onto the enterprise cloud here.
The deployment took a couple of months, and to draw the schema and design the other requirements took three to four months.
I will be using the enhanced version when we set it up for the customer.
What about the implementation team?
We have a team in our organization to maintain this solution.
Which other solutions did I evaluate?
We evaluated other options as well, but we choose Couchbase for the immediate consistency with Elastic, and the real-time native replication plugin, which is fantastic!
What other advice do I have?
I plan to be using the enhanced version.
I would definitely recommend this solution to anyone who is interested in using it.
The enterprise version is a more stable version. The indexing is very powerful and the N1QL is especially useful when you come from an SQL background. It will be very powerful.
This is why I would recommend Couchbase. To this point, I have never needed anything extra added to it.
I am very happy with this solution, and I would rate Couchbase a nine out of ten.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Which version of this solution are you currently using?