Hey! Here’s where we stand:

I have largely completed the gigantic rework of schema internals required to do the dynamic schemas we need for stitching.

We also have support for SDL based schemas, and thus by extension introspection based schemas.

So, what remains?

• Various mechanics around how to dynamically update these schemas.
• Lots of questions about the client side of this. This has the most work remaining to it. I really need to dig into what other clients are doing, is there even a suggested spec for how this works?

There’s also a handful of small internal changes to do, but that encompasses the bulk of the remaining work.

My team has released an example app that does Schema Stitching in Absinthe…

Eventually I’d like to see some form of this make it into Absinthe itself, but there are lots of decisions to make about how to accomplish that. Meanwhile, those who really want to get something up and running can check out what we did in our API at New Relic.

The main feature in 1.5 is really that schemas can be built and manipulated with ordinary datastructures, and constructed from sources like SDL and the traditional macros. This was a prerequisite to any kind of dynamic programatic schema building, whether that was going to happen via schema stitching or the new federation mechanism.

Honestly no. It’s in Beta now and the beta is pretty solid, all 904 tests pass in the Absinthe suite. With Bruce at Github now and with me taking over engineering at Cargosense we’ve been too busy to commit large chunks of time in a way that would provide a predictable release schedule. @binaryseed has been a fantastic addition to the core team, but we’re still not in a place where we can make a meaningfully accurate prediction.

Can’t wait for the 1.5 version. Our whole infrastructure is based on micro services and I’m having a hard time on the implementation of fields with different back-ends.

Any ideas on the date? I can see at least 3 alpha version in GitHub