AApplexTechFedCLI

Database support

Operate relational and non-relational systems through one CLI.

FedCLI includes built-in integrations for common operational, analytical, document, key-value, graph, search, and time-series systems, with a plugin path for additional JDBC targets.

Built-in engine coverage

Relational and warehouse

Apache Derby, PostgreSQL, MySQL, SQLite, Oracle Database, SQL Server, Sybase ASE, IBM DB2, Snowflake, Amazon Redshift, Databricks, ClickHouse, MariaDB, and H2.

Document, key-value, and search

MongoDB, Redis, Elasticsearch, AWS DynamoDB, and GCP Bigtable.

Graph and time series

Neo4j, Cassandra, and InfluxDB 1.8.

Drivers and access

Some vendor drivers or credentials have their own installation, licensing, network, and security requirements. Validate those prerequisites for the target environment.

Plugin databases: extend JDBC coverage at runtime

FedCLI can add an available JDBC driver at runtime when a database is not part of the built-in catalog. Common plugin-path targets include CockroachDB, HSQLDB, Firebird, Informix, Presto, and Trino. The plugin search queries Maven Central, so availability, driver licensing, Java compatibility, and database-specific behavior must be confirmed for the selected artifact.

Plugin databases gain the core connection and SQL-oriented workflow; they do not automatically have the same native command depth as every built-in provider.

PLUGIN SEARCH hsqldb;
PLUGIN ADD hsqldb;
CONNECT 'jdbc:hsqldb:mem:demo';

Validate before operational use

  1. Confirm the vendor driver and Java compatibility for the target.
  2. Connect with the least-privileged database identity appropriate for the task.
  3. Inspect tables, collections, schemas, or indexes before automation.
  4. Test the exact query and export behavior on representative non-production data where possible.