[sandstrom]

We've looked at GraphQL but ended up going with Graphiti instead.

Only a few weeks since we implemented, but happy so far. Feels like it's the best of REST and GraphQL.

This page from Graphiti[1] explains the thinking behind it. Don't be discouraged by the loud pink colors ;)

[1] https://www.graphiti.dev/guides/why

[Deimorz]

Thanks - I hadn't heard of Graphiti before, but it looks really interesting. I like a lot of the aspects of its design and capabilities, I'll definitely need to read more about it.

[xtagon]

It's strange to me that they pointed out Domain Driven Design without any mention of CQRS (which isn't strictly linked to DDD, but is commonly associated) or how Graphiti would help with some of the pitfalls of CRUD-based APIs. In fact, earlier in the post they point out that the built in "verb" links feature only works with CRUD, and all of there examples are CRUD based.

[mdaniel]

I guess I shouldn't complain in a thread about GraphQL on Rails, but it's disappointing that Graphiti appears to be only for Rails, and not a general purpose mechanism/specification like GraphQL that it complains about

[SketchySeaBeast]

I was excited to look at a REST/GraphQL alternative, but that website doesn't fill me with a lot of excitement or enthusiasm. The styling choice is fairly off-putting, and the first line of the "why" has a misspelling.

[sandstrom]

Yeah, I know, it's subjective but I also think the design is awful. It's good software though!