May 2017
Beginner to intermediate
596 pages
15h 2m
English
Since we have already covered why we have chosen REST over SOAP, we thought we have to definitely bring GraphQL as well into a brief discussion.
One of the main requirements from a Data Lake is to cater to a variety of consumers. Each consumer has different requirements on what are the attributes that they want and in what format. Usually according to requirement of the consumer more endpoints have to be created. Over the period of time this can grow and can soon become a maintenance problem.
GraphQL takes out some aspects of this but not having to write different services according to attribute requirements for a model catering to a consumer.