But there are still GraphQL and disadvantages that can make development difficult:
Incompatibility with old backend applications. Developer resources are limited, and getting programmers to remake an old architecture requires a lot of negotiation time. Also, there are still concerns that GraphQL will eventually lose relevance and all the work will be in vain.
GraphQL responses are large. If a standard JSON response with similar data weighs 100 KB, then its GraphQL counterpart can reach several megabytes. Therefore, in some cases, you have to use the good old JSON.
As the number of clients increases, the Node. js can be overloaded. This can be fixed by running it in multiple threads. True, then there will be a problem with synchronization, but it can also be solved.
Each developer can evaluate for himself what will outweigh in the case of his project: the advantages of GraphQL or its disadvantages. The X5 team decided for themselves that they would continue to use this system, as the wide choice of tools makes it flexible enough for their development area.