Hello, scf, you wrote: scf> the Link: http://graphql.org scf> Briefly: the New approach to creation network API, giving the data in the form of JSON. It is interesting simple, including in implementation, and powerful language of requests. scf> Someone already picked? Perhaps, used? I used graphql-java (it is a server part for Java - the interpreter of requests and their performance). You write subject model and fasten itself (in my case it there was simply a graph of invariable objects in storage). GraphQL it is faster not language of requests (as, for example SQL), it is faster language of a filtration of the data. You give the universum of the data, and the client can select that slice which is interesting to it. In it there is a concept of parameters which can influence the returned data (that does it a bit similar to language of requests), but the request structure is beaten by nails (circuit). For example, the client cannot pull out or do the arbitrary pieces any join. For example, if your circuit contains a field "user" at which there is a field "company" you cannot to make request at once since a field "company" if it in the circuit explicitly it is not set. Allows to solve a problem of nonoptimal requests (N+1 or too a considerable quantity of the data) in REST thus without leading to one million possible parameters (type "includeUsers=true/false") or to nonoptimal answers (it is returned everything, and the client understands). In my opinion, it well approaches and to interactions the server-server. For example, we had a project to do integration with indirect systems through GraphQL. For a client - server (for example, a web application - the server) is fashionable to think now of more generalized protocols (ideas can be peeped, for example, here: http://tonsky.me/blog/the-web-after-tomorrow/), but it so while it is more than a manner, in my opinion (though I similar now just do something that is amusing, atop REST API).