Title: Hey HN,<p>I&#x27;m excited to share Orbital, a new approach for unifying APIs and Data sources!<p>Rather than relying on glue code to bridge endpoints, Orbital leverages annotations in schemas &amp; API specs to build the integration dynamically.<p>The traditional method of crafting glue code often becomes repetitive and burdensome to maintain in the long run.<p>With Orbital, developers embed tags to their existing API specs (OAP, Protobuf, etc), indicating where data can be sourced, and publish these specs to Orbital (which runs self-hosted).<p>Consumers query these tags with our TaxiQL language, 
and Orbital generates the integration on the fly. That could be merging multiple APIs, blending API and database queries,
or enriching event streams to craft custom message payloads.<p>It feels a lot like writing GraphQL, but there&#x27;s no resolvers to maintain, and producers are free to use a variety of API Spec languages.<p>The beauty of using tags over field names is the adaptability. As API developers update and publish their specs, the integration remains seamless and automatically adjusts.<p>Under the hood, the tags (and associated query language) are actually Taxi - an OSS meta-language and toolchain we build (and have shared previously).  Orbital is a query engine that executes TaxiQL queries, generating the integration.<p>We&#x27;ve been working on this for a while, and have a number of production deployments. We recently made the move to make the source available on Github under a mix of Apache 2 (Open Core) and BuSL.<p>In a nutshell, Orbital excels in Data Composition (covering APIs, DBs), crafting Bespoke Event Streams, and streamlining ELT workloads into databases.<p>Excited to hear your thoughts and feedback!
Upvote: