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 the Server — whether Capella, or your own self-managed 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 Couchbase Server release (note, Capella always runs a recent version of Couchbase Server).
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 Scala 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-priveleged 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.
For the Scala SDK, that is to keep a separate properties file for your development and production environments.