Basically we have clusters, Couchbase clusters, databases, and that is how we use Couchbase with XDCR. All the clusters are set up and then we use Couchbase. It is a complex application setup we use with Couchbase. We have replication and multi-node Couchbase setup.
I have two use cases right now. I have a shopping list app where users can share their lists, so I used the Sync feature with Sync Gateway.In another product, I use what they call N1QL, which is a query language, and I use it to check if ads are available to show to a user. In one part of the product, I only use the Sync Gateway, and in another part, I use N1QL to query the database.
We used Couchbase ( /products/couchbase-reviews ) as the primary data storage. Since our company was in the gaming industry, Couchbase ( /products/couchbase-reviews ) stored data on players and related to games, levels, and similar objects for our mobile applications, aka games. There was a synchronization in place between Couchbase and another database, Elasticsearch. Some indices from Couchbase were periodically replicated to Elasticsearch.
Our primary use case for Couchbase is related to the iGaming industry, particularly for high-performance reads and writes to meet our SLA for high volumes. We have a particular use case where there is an SLA of one second, and Couchbase is critical for ensuring our wallet operations function correctly.
In my company, we use the enterprise version of Couchbase, and it is used across the organization for its database operations. We do only use the NoSQL database, not Couchbase Capella. The tool is mostly for document-based storage of Cisco, which is a retail company. We manage a lot of product information and send a lot of metadata that we generate for all of our orders, including baskets and other aspects. We use Couchbase heavily for document-based storage purposes.
Associate Principal Performance Engineer at Aptos Retail
Real User
Top 5
2024-07-30T17:00:00Z
Jul 30, 2024
Initially we were using the on-premise Couchbase Server which was maintained by the organisation with assistance from a consultant from Couchbase. After they came up with the cloud version of Couchbase called Capella, it was decided to migrate there to reduce the maintenance cost and to take advantage of the advanced features the product offers. Couchbase Capella offered distinct advantages like ease of horizontal and vertical autoscaling, ease of querying using the SQL++ language (which is not hard to learn), and the flexibility it offers while being hosted in the cloud and being served by the parent company.
CTO Architect at a financial services firm with 10,001+ employees
Real User
2023-01-13T01:04:37Z
Jan 13, 2023
We're in the middle of building out a persistent cache layer using Couchbase. That's across multiple international regions, but we have other instances where we're using it for data stores and some for its analytics features.
Senior Software Engineer at a retailer with 10,001+ employees
Real User
2023-01-10T19:13:17Z
Jan 10, 2023
I was working on a game called Infinite Fleet and the backend for that particular game was written in Golang and our database of choice was Couchbase. We were dealing with a lot of unstructured data and were leveraging the load balancing capabilities of Couchbase. The data that is stored on our Couchbase instances includes player profiles and metrics. We have a total of 25 developers who use it.
Backend Developer & Team Lead at Osiris Trading powering Betway
Real User
2022-12-21T14:56:30Z
Dec 21, 2022
In the beginning, we used this solution to store configuration data. We had a system that we used for management for our platforms. We then needed a system that could help with configuration of platforms. We were looking at a couple of different options of how to store those configurations dynamically. We have 17 people that use this solution in total. It took us a while to figure out how to use this solution.
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.
Senior Android Developer at a tech services company with self employed
Real User
2020-11-18T20:57:00Z
Nov 18, 2020
There are many shifts and we use Couchbase to log that data whenever they travel from one place to another. We log the data and we merge it in the backend. That's how the application and everything works. If you are a temp person on one shift and you have logged data, we use the nearby API to connect them and to pull and push each other's data. We also use Couchbase for Android tablet to the cloud.
Couchbase Enterprise offers powerful data management capabilities with features like horizontal scalability, ease of use, and flexible tools for business applications. Designed for high performance and reliability, it supports multi-master capability and low latency, making it ideal for dynamic environments.Designed for businesses needing crucial data management, Couchbase Enterprise offers advanced indexing, analytics engines, and efficient storage for performance enhancement. It provides...
Basically we have clusters, Couchbase clusters, databases, and that is how we use Couchbase with XDCR. All the clusters are set up and then we use Couchbase. It is a complex application setup we use with Couchbase. We have replication and multi-node Couchbase setup.
I have two use cases right now. I have a shopping list app where users can share their lists, so I used the Sync feature with Sync Gateway.In another product, I use what they call N1QL, which is a query language, and I use it to check if ads are available to show to a user. In one part of the product, I only use the Sync Gateway, and in another part, I use N1QL to query the database.
We used Couchbase ( /products/couchbase-reviews ) as the primary data storage. Since our company was in the gaming industry, Couchbase ( /products/couchbase-reviews ) stored data on players and related to games, levels, and similar objects for our mobile applications, aka games. There was a synchronization in place between Couchbase and another database, Elasticsearch. Some indices from Couchbase were periodically replicated to Elasticsearch.
Our primary use case for Couchbase is related to the iGaming industry, particularly for high-performance reads and writes to meet our SLA for high volumes. We have a particular use case where there is an SLA of one second, and Couchbase is critical for ensuring our wallet operations function correctly.
In my company, we use the enterprise version of Couchbase, and it is used across the organization for its database operations. We do only use the NoSQL database, not Couchbase Capella. The tool is mostly for document-based storage of Cisco, which is a retail company. We manage a lot of product information and send a lot of metadata that we generate for all of our orders, including baskets and other aspects. We use Couchbase heavily for document-based storage purposes.
Initially we were using the on-premise Couchbase Server which was maintained by the organisation with assistance from a consultant from Couchbase. After they came up with the cloud version of Couchbase called Capella, it was decided to migrate there to reduce the maintenance cost and to take advantage of the advanced features the product offers. Couchbase Capella offered distinct advantages like ease of horizontal and vertical autoscaling, ease of querying using the SQL++ language (which is not hard to learn), and the flexibility it offers while being hosted in the cloud and being served by the parent company.
We manage our telecommunication application using the product.
We're in the middle of building out a persistent cache layer using Couchbase. That's across multiple international regions, but we have other instances where we're using it for data stores and some for its analytics features.
I was working on a game called Infinite Fleet and the backend for that particular game was written in Golang and our database of choice was Couchbase. We were dealing with a lot of unstructured data and were leveraging the load balancing capabilities of Couchbase. The data that is stored on our Couchbase instances includes player profiles and metrics. We have a total of 25 developers who use it.
In the beginning, we used this solution to store configuration data. We had a system that we used for management for our platforms. We then needed a system that could help with configuration of platforms. We were looking at a couple of different options of how to store those configurations dynamically. We have 17 people that use this solution in total. It took us a while to figure out how to use this solution.
We're using Couchbase for general purposes and for caching.
In our current project, we use this solution in the healthcare field for the telemedical industry and in other projects in the automation industry.
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.
There are many shifts and we use Couchbase to log that data whenever they travel from one place to another. We log the data and we merge it in the backend. That's how the application and everything works. If you are a temp person on one shift and you have logged data, we use the nearby API to connect them and to pull and push each other's data. We also use Couchbase for Android tablet to the cloud.
We use it for data link utilization.