-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
apollo-android
:robot: A strongly-typed, caching GraphQL client for the JVM, Android, and Kotlin multiplatform.
-
learning-graphql-client
A GraphQL client utilizing a publicly available GraphQL endpoint and read some data from it.
I am planning to consume a graphql service in a java dropwizard microservice. I would like to know whether there are some easy plugin types of libraries available out there. I tried using apollographql, the automatically created schema files are not serialized, which makes the parsing tough. Planning to explore graphql-query-builder and graphql-java, any other suggestions are welcome.
I am planning to consume a graphql service in a java dropwizard microservice. I would like to know whether there are some easy plugin types of libraries available out there. I tried using apollographql, the automatically created schema files are not serialized, which makes the parsing tough. Planning to explore graphql-query-builder and graphql-java, any other suggestions are welcome.
Hi 👋Martin from https://github.com/apollographql/apollo-android here. Can you ellaborate more on "created schema files are not serialized" ? For Android app, I usually recommend separating the persistence layer and the network models so that they're not coupled. But maybe it's different from a microservice?
Thanks a lot for showing interest and replying to my question. I am kind of new to apollographql. At work, I have a requirement to consume a graphql service. I tried to use apollographql for consuming it, really liked the non-blocking call (even though I didn't utilize it). I tried to convert the response to String using Jackson (ObjectMapper) and it failed with an error saying `No serializer found for class`. I tried to do similar connectivity at learning-graphql-client and it worked fine. Since the models are derived from schema.json, I expect the generated classes to be easily parsable. But it was not the case for the generated file, which I used at work.