Product and content catalogues
We can model products and content with different attributes as documents, designing updates and queries alongside the application.
Application data with Couchbase.
We design applications using product, customer and operational data with the JSON document model and SQL++ queries.
Tell us what you needWhere it fits.
We assess potential uses for Couchbase against your work and existing systems.
User and customer data
For applications using profiles and preferences, we define the data model, access needs and update flows.
Queries and application workflows
We assess key-value access and SQL++ queries for the need. Index choice and query behavior depend on the data and workload.
How we can help.
We define the scope around your needs, existing systems and team priorities.
Data model and queries
We design document structures, key-value access, SQL++ queries and indexes around existing data and business rules. We assess Search Service and vector search for the version and deployment.
Explore AI-assisted development with AI LABSIntegration and data migration
We connect applications to Couchbase through appropriate clients and services. Where needed, we plan data migration, offline work with Couchbase Lite and server synchronization.
Explore software development with Reformo (opens in a new tab)Testing and operational readiness
We evaluate queries, concurrent updates and, where relevant, synchronization conflicts against representative workloads. Backup, access and monitoring needs are defined within the project scope.
Explore training and mentoring with HGM Labs (opens in a new tab)Example scenarios.
These examples illustrate what could be built for different needs.
Explore 16 use cases
- SQL++ query
- Query Service
- JSON documents
- Filtered results
Query Service and suitable indexes need to be configured in the deployment.
Products with different attributes
A catalogue application can store products with different fields as documents. Queries and indexes can be designed for the filters customers need.
Customer profiles
An application can use customer preferences and profile information, with update and access rules defined for the relevant workflow.
More use cases.
These scenarios illustrate potential applications. We assess the requirements of the chosen version and deployment together at the start of a project.
Document model and application data4 examples
Document structure, key-value access and SQL++ queries are designed around the application’s data model and indexes.
- Product variants. A catalogue can store products with different attributes as JSON documents and query by category or attribute.
- User preferences. An application can store preferences in a profile document and use them in relevant screens, with access rules defined separately.
- Content publishing. A content application can query documents for publication using fields such as language and publishing status.
- Cart updates. A shopping cart can be stored as a document, with update and conflict rules for concurrent changes.
Querying and search4 examples
Full-text search uses Search Service. In Couchbase Server 7.6 it supports vector search; version 8.0 adds vector indexes for Query Service. Platform, deployment and license requirements must also be checked.
- Filtered catalogue. SQL++ queries and suitable indexes can list products by brand, category or attributes within a document.
- Full-text search. Search Service can provide text search over product names and descriptions alongside application filters.
- Semantic content search. With a compatible embedding model and index, an application can find content similar to a user’s question.
- Text and similarity. On a suitable Search Service version, text matches and vector similarity can be considered together in a search workflow.
Offline work and synchronization4 examples
These examples require Couchbase Lite on the device and Sync Gateway or Capella App Services for server synchronization. Supported platforms, versions, licenses and conflict rules must be assessed.
- Field inspection. A field worker can record checklist items offline and synchronize them when connectivity returns.
- Service tasks. A technician can view tasks synchronized to the device and record job notes while offline.
- Inventory counts. A team can record counts offline; conflict rules handle changes from different devices during synchronization.
- Field forms. A field application can store and synchronize form data, with access to records defined for each user.
Workflows and operations4 examples
Updates, consistency and service features are tested against the workflow, chosen version and deployment.
- Order status. Order documents can be updated as their status changes; transaction boundaries are defined by the business rules.
- Account settings. Application or account configuration can be read by key and updated by authorized operations.
- Migrating existing data. Source records are mapped to the document model, then fields and sample queries are compared after migration.
- Reviewing indexes. A team can assess indexes, data freshness and operational needs against representative queries and workload.
Product documentation: Couchbase vector search documentation (opens in a new tab) · Couchbase Mobile documentation (opens in a new tab)