01 / Silos
Cross-system analysis becomes ETL
A simple join can trigger another extraction pipeline, staging area, and copy of sensitive operational data.
Solution · Federated data access
Query distributed databases as one SQL system
Run read-only SQL across isolated Gluesync agents through one JDBC endpoint—without first copying raw data into a central warehouse.
- 01 Use one JDBC endpoint
- 02 Resolve a federated query
- 03 Combine read-only results
The challenge
Some questions span systems
Operational data remains distributed across engines, networks, and ownership boundaries even when teams need one answer.
02 / Access
Clients need many credentials
Each database connection adds secrets, network routes, drivers, and governance work for every consumer.
03 / Control
Ad-hoc queries can affect production
Unbounded access risks expensive scans, writes, and resource contention on operational databases.
How it works
One gateway, distributed execution
Query Forge exposes Gluesync-connected databases through a branded JDBC endpoint and executes work close to each agent.
- 01
Connect
Use one JDBC endpoint
BI tools and SQL clients connect through jdbc:gluesync instead of opening a route to every database.
- 02
Plan
Resolve a federated query
The gateway identifies participating agents and pushes eligible filters and projections toward each source.
- 03
Return
Combine read-only results
Query Forge joins the result sets and returns one SQL response without creating a central raw-data copy.
Gluesync capabilities
Federation with access boundaries intact
Query Forge combines familiar SQL connectivity with scoped authentication and safe execution defaults.
01
Cross-agent SQL
Join relational and supported non-relational systems behind different agents from one query.
- Apache Calcite planning
- Filter and projection pushdown
- Heterogeneous schema access
02
JDBC for existing tools
Connect familiar clients and BI applications through the Gluesync JDBC driver.
- jdbc:gluesync endpoint
- DBeaver and DataGrip workflows
- Tableau-compatible connectivity
03
Role-aware access
Authenticate with local credentials or Personal API Tokens, with access bounded by the user's permissions.
- Read-only execution
- Scoped PAT access
- User-bound authorization
FAQ
Frequently asked questions
Answers about Query Forge, cross-system SQL, JDBC connectivity, and governed read-only access.
What is a federated query?
A federated query reads and combines data from multiple systems through one query interface without first copying all participating data into a central store.
How do clients connect to Query Forge?
SQL clients, BI tools, and applications connect through the Gluesync JDBC endpoint instead of opening a separate database connection to every source.
Can Query Forge join data across different database engines?
Yes. It can plan read-only SQL across supported systems behind different Gluesync agents and combine the resulting data into one response.
How is federated access controlled?
Requests are authenticated with Gluesync credentials or Personal API Tokens and remain bounded by the caller's permissions, with read-only execution as the safe default.
Ask cross-system questions without building another copy
Explore Query Forge or talk with MOLO17 about federated access across your connected database estate.