Introducing The Bridge: Declarative Dataflow for GraphQL (Developer Preview)

[aarne]

Hey everyone! 👋

We’re excited to open up early testing and discovery for The Bridge (@stackables/bridge).

If you’re tired of hardcoding third-party SDKs and scattering external API keys across every microservice in your architecture, we built this for you.

The Bridge allows you to build a lightweight, unified internal gateway that routes, reshapes, and secures all traffic to external providers using a declarative Data Topology Language. You define a clean, strongly-typed internal interface, and The Bridge wires that interface to the outside world using static .bridge files.

🌉 What makes it different?

Unlike writing sequential JavaScript or Python integration code, .bridge files are static circuits. You don't write scripts; you wire data.

• Resolves Backwards (Pull, Don't Push): It traces demand from the client request back to the external API payload. If your internal service doesn’t request a field, that wire is "dead"—no code runs, and no unnecessary external API calls are made.
• Parallel Async Orchestration: When wrapping multiple REST services into a single GraphQL query, the engine automatically executes all required HTTP calls concurrently. No more writing manual Promise.all logic—the topology resolves itself in parallel optimally.
• Overloading Support: Data can be fetched via multiple wires concurrently, allowing the engine to automatically resolve using the cheapest or fastest path.
• Declarative Resiliency: Layered, built-in fallbacks (|| for nulls, ?? for errors, on error for tools) compose like a Postgres COALESCE.
• LLM-Native: Because it describes a static graph of intent rather than sequential execution, it is incredibly easy for LLMs to generate and for humans to visually review.

🚂 The Sweet Spot: Controlled Egress & Provider Agnosticism

We've found this approach is a game-changer for Egress Control.

Instead of installing the SendGrid SDK into Service A and Service B (and leaking credentials to both), you stand up a Bridge gateway. Your services simply make a standard HTTP POST request to a clean sendEmail endpoint. The gateway uses your logic.bridge file to map the request, inject the central API keys, and route the traffic.

Need to swap from SendGrid to AWS SES, or Stripe to Braintree? You just rewrite the .bridge file. You don't touch a single line of your calling services' code.

This is not ready for production yet. We are deliberately keeping things fluid so we can iterate fast. Breaking changes to the .bridge language and TypeScript API will occur frequently as we lock in the design. We will switch to strict SemVer starting from v2.0.0.

🤝 We want to work with you!

Right now, we are actively looking for interesting use cases and early adopters to help us stress-test the language design and feature set before a stable release.

• Are you building an egress layer for messy third-party providers?
• Connecting and orchestrating internal REST services into a clean GraphQL graph?
• Trying to enforce single exit points for security and vendor allowlisting?

If you have a use case you think would be a great fit, we want to hear about it. Drop into our GitHub Discussions, share what you're trying to build, and let's figure out how to wire it up!

Happy wiring! ⚡️