Compare / Contrast JSON API and GraphQL

[undiwahn]

One very obvious question that potential users will have is:

Why should I use this instead of JSON API or GraphQL?

We should address this head on in the documentation.

Some points to consider:

• Simplicity (+ for Popcorn)
• Performance in regards to consuming output (Potential + for Popcorn, maybe + for GraphQL too)
• Implementation provided (+ for Popcorn for .net at least!)
• Popcorn can fairly seamlessly integrate with an existing API without changing the schema

We need to provided researched pros and cons.

[alexbarbato]

Just jotting down some stuff I'm finding/thinking:

JSON API: It's a standard (that has pluses and minuses) Technically, due to the fact that JSON API is a standard, it's a bit correlary to Popcorn as we COULD make popcorn an implementation of JSON API

• flexibility costs
• potentially easier to integrate (but that is heavily project dependent)
• Lots of implementation tools to ease the burden of implementation

GraphQL: In a lot of ways this is a complete deviation from REST so I imagine it's adoption would definitely be tied heavily to someone's desire or willingness to depart REST for a newer system and way of viewing/accessing the information on the server. Performance and ease of use are certainly factors to consider (particularly with regards to .NET)