tecknolab/dbcloudbin-cli repository overview

DBcloudbin (https://www.dbcloudbin.com⁠) is a data management optimization solution for large databases (Oracle, SQL Server as of today). It enables offloading data to efficient and cheap object storage (Cloud or on-premises) without any application change nor re-Engineering. It uses an data virtualization technique, so that the application can remain accessing data through SQL queries and DBcloudbin is in charge of fetching the offloaded data and injecting it into the final query results.

The running components that make up a DBcloudbin installation are mainly two:  

• DBcloudbin agent, to process all the requests launched by the CLI or indirectly by your application through SQL queries.
• DBcloudbin CLI tool, to launch the common tasks as executing archive or purge operations.

IMPORTANT! This will not avoid the usage of DBcloudbin setup to configure the Database layer and adaptation of your application schema using the regular DBcloudbin install tool (you can request a FREE trial here⁠). However you can install only the first two packages running the setup from any server or laptop with access to your database, and leave the agent and CLI running as Docker containers.

The dbcloudbin-cli image can be customized through the following environment variables:

• AGENT_HOST: The host (or container name) where the agent is running. By default, "dbcloudbin-agent".
• AGENT_PORT: The advertised agent port, by default 8090.
• AGENT_PROTOCOL: The protocol used to connect to the agent. By default, "http" but depending how you are using your Docker/Kubernetes infrastructure, you may be using a https network load balancer, so this parameter would be set to https.

Use the CLI with a docker command as the following (in this example a dbcloudbin-agent container must be running):

docker run --rm -it tecknolab/dbcloudbin-cli:3.04.02 info

With the first launch, a CLI wizard will request us the target database credentials (that is the credentials of your application schema, the one selected in the setup for generating the transparency layer). To avoid introducing your database credentials every time you execute a DBcloudbin command, you must add an external docker volume mapped to the /profiles path. 

docker run --rm -it -v ~/my_profiles:/profiles tecknolab/dbcloudbin-cli:3.04.02 info

For additional information, check the blog entry: https://www.dbcloudbin.com/docker-kubernetes⁠