> 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:
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 :)
From the site, it reads:
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-id...
- https://smithy.io/2.0/index.html