Please use the form below to provide your feedback. Because your feedback is valuable to us, the information you submit in this form is recorded in our issue tracking system (JIRA), which is publicly available. You can track the status of your feedback using the ticket number displayed in the dialog once you submit the form.

Deployment

      +
      Transition from dev environment to prod, and keep up with the latest fixes.

      One of Couchbase’s strengths is speedy response, so deployment of apps should be in the same region as your Analytics cluster.

      We always recommend the latest version of the SDK. This not only contains the latest security updates and bug fixes, but will be compatible with the latest Enterprise Analytics release.

      Before deploying, take note of any compatibility issues for the language platform and underlying OS. The full installation guide should cover any special cases for all supported environments.

      Development & Testing Environments

      During development, some shortcuts are taken to get up and running which would not be acceptable during deployment. These include use of administrator permissions, connecting from your laptop instead of a secure app server, and even disabling certificate verification for TLS. Testing environments may also differ from deployment.

      The Go Analytics SDK docs note whenever a shortcut is being taken, but here is a non-exhaustive list of those development practices which should not be carried over to production deployments:

      • Over-privileged access

      • Geographical separation of app server and database

      • Skipping certificate verification

      The best way to accommodate developing an application that is to be deployed to production is to use the platform’s default approach for configuration files.