Description

Graphql fits exactly into our component-based architecture. The components control what they need for the data. It solves REST problems, such as establishing multiple connections or downloading redundant data. However, it brings other problems among other things it sends data only when it gets all the hard to set up their streaming. On the other hand, graphql has similar disadvantages as SOAP.

Plus

1. Aligned with our architecture
2. Component focused
3. Typed language - aligned with Typescript

Cons

1. Hard to work with caches
2. Hard or even impossible setup response streaming