There are two essential concepts for integration today: APIs and events. APIs allow for reading and writing data, calling functionality and starting processes. APIs connect us with actuators in the digital world that enable us to do and change things.
GraphQL queries consist of one or more patterns which are matched against the big graph containing all the data on the server. The patterns describe a subgraph of the big graph and is used to search for the relevant data in the
To read data with GraphQL, the client uses the query method. In the pattern of this query, the client has to explicitly specify all the object and fields it is interested in. As a result of the query, the client
Modern clients need to get near real-time updates that get triggered when something changes on the server. For example, an instant messaging app needs to get notified, when a new message arrives on the server, or a weather app needs
A graph is a very generic data structure, so it should be possible to express the data of any application in the form of a graph. And this graph, formed by all application data, is what we call the
Let me show you what I mean, when I say, events are everywhere where there are APIs: Payment API: An event notifies when the payment was processed. SMS API: An event notifies when the SMS is delivered. Email API: An event notifies when