2 ms·

I agree that querying is where the real value is at, and Trustfall looks like an elegant approach. While Taxi is all about documenting & augmenting specs, Orbi

I agree that querying is where the real value is at, and Trustfall looks like an elegant approach. While Taxi is all about documenting & augmenting specs, Orbital is the query engine (which is a bit similar to Trustfall) that consumes those specs. Orbital's goal is to allow consumers to be able to query for data, without having to be aware of the specifics of the data sets / APIs / DBs, etc they're composing together. IMO GraphQL does a nice job on the query side of keeping consumers away from the wiring, but shifts the obligation to middleware resolvers. How data is wired together is ultimately an implementation detail, and one that changes. If consumers need to know about how stuff is connected, they're subject to breakages when those details change.

gavinray 3y ago
> GraphQL does a nice job on the query side of keeping consumers away from the wiring, but shifts the obligation to middleware resolvers. I'm not sure that I understand how Orbital is different from tools that autogenerate GraphQL API's on top of data sources like databases and API's. From the site, it reads: > "Orbital uses your existing API specs and Database schemas - enriched with Taxi metadata to describe links. Orbital turns this into rich API and data catalog, letting you explore all your data, and how it connects." It sounds like the same concept, except using a new language instead of GraphQL? The schema language looks very similar to something AWS has called Smithy by the way: - https://aws.amazon.com/blogs/developer/introducing-smithy-idl-2-0/ https://aws.amazon.com/blogs/developer/introducing-smithy-id... - https://smithy.io/2.0/index.html https://smithy.io/2.0/index.html
- martypitt 3y ago
  Autogen tools do a nice job of creating GraphQL schemas from a single source. We're looking more at how to compose / stitch multiple sources into a single queryable API. (ie., Stitch data from a DB, some REST APIs, and a Kafka topic). In GraphQL, you need to write / maintain resolvers that handle the stitching for you - which means as upstream data sources change, resolvers need to be maintained too. Smithy is nice, and we'll probably add first-class support in Orbital for it at some point. Taxi was around before Smithy, so we're the OG :)
nextaccountic 3y ago
> Orbital is the query engine So I searched and https://github.com/orbitalapi/orbital https://github.com/orbitalapi/orbital says to use https://hub.docker.com/r/orbitalhq/orbital https://hub.docker.com/r/orbitalhq/orbital which has no README It also says "This repository will contain our open source code, along with issues, discussions and roadmap.", is there an ETA for source code release? Will the Java application in that docker container be open sourced?

gavinray 3y ago

> GraphQL does a nice job on the query side of keeping consumers away from the wiring, but shifts the obligation to middleware resolvers. I'm not sure that I understand how Orbital is different from tools that autogenerate GraphQL API's on top of data sources like databases and API's. From the site, it reads: > "Orbital uses your existing API specs and Database schemas - enriched with Taxi metadata to describe links. Orbital turns this into rich API and data catalog, letting you explore all your data, and how it connects." It sounds like the same concept, except using a new language instead of GraphQL? The schema language looks very similar to something AWS has called Smithy by the way: - https://aws.amazon.com/blogs/developer/introducing-smithy-idl-2-0/ https://aws.amazon.com/blogs/developer/introducing-smithy-id... - https://smithy.io/2.0/index.html https://smithy.io/2.0/index.html

martypitt 3y ago
Autogen tools do a nice job of creating GraphQL schemas from a single source. We're looking more at how to compose / stitch multiple sources into a single queryable API. (ie., Stitch data from a DB, some REST APIs, and a Kafka topic). In GraphQL, you need to write / maintain resolvers that handle the stitching for you - which means as upstream data sources change, resolvers need to be maintained too. Smithy is nice, and we'll probably add first-class support in Orbital for it at some point. Taxi was around before Smithy, so we're the OG :)

nextaccountic 3y ago

> Orbital is the query engine So I searched and https://github.com/orbitalapi/orbital https://github.com/orbitalapi/orbital says to use https://hub.docker.com/r/orbitalhq/orbital https://hub.docker.com/r/orbitalhq/orbital which has no README It also says "This repository will contain our open source code, along with issues, discussions and roadmap.", is there an ETA for source code release? Will the Java application in that docker container be open sourced?