At Dgraph, we really care about our community. We are proud to announce our first ever Dgraph community call on 2020-08-13T17:30:00Z. I’ll be leading the call, along with @dmai (Community Lead), @ibrahim (Badger maintainer) and other team members.
Dgraph’s Savvy Shuri release (20.07.0) is out and we are excited to share all the new features with you. This call is also a great place to bring your questions and comments about using Dgraph for your project.
Our goal is to make this call as interactive as possible, please register here and take some time to post your questions on this thread ahead of time.
Agenda
Introduce new features in 20.07.0 Savvy Shuri release (10-15 mins)
Questions from the community. Please post your questions in this topic. (45 mins)
I would like to see some real use-case of dgraph combined with GraphQL.
Use-case which involves some Logic beyond the autogenerated CRUD operation. Some examples are:
Connectors (graphql spec)
Integration with Middleware like Apollo and the implementation of custom queries and fields
Filter by nested node using Middleware like Apollo
What is the timeline for integration with kafka? In the meantime what are the best practices for streaming data into dgraph?
Is it possible to use the dgraph4j client to cancel a request after it’s been sent to the server? I’ve used the dgraph client with an interceptor and triggered a cancel that way, but I’m wondering if that actually cancels the query being run on the alpha.
I’ve noticed that earlier versions of dgraph (e.g., v1.1.1) have significantly better performance with certain kinds of queries (eg, those with Type filters) than newer versions. What is the status of the Query Planner?
ETA for implementing count on the graphql endpoint taking into consideration auth rules. I can count all using a DQL custom field but then that does not take into consideration any auth rules.
ETA for any kind of @math support in graphql Not requested yet, but a feature in DQL not in graphql mentioned in GraphQL+- -> Spec Compliant GraphQL
Any other upcoming plans on performance increases to increase speed and reduce memory usage. I understand these two don’t go together too well and are usually inversely related. Not saying it is horrible right now, but Memory requirements are through the roof compared to other non graph DBs.
Dgraph GraphQL deals with authorization, but is completely flexible about how your app does authentication. You could authenticate your users with a cloud service like OneGraph or Auth0, use some social sign in options, or write bespoke code. The connection between Dgraph and your authentication mechanism is a signed JWT - you tell Dgraph, for example, the public key of the JWT signer and Dgraph trusts JWTs signed by the corresponding private key.
However I don’t want to use AuthO so I didn’t follow along. Maybe I’ll do it later if I don’t have a choice.
I put my request here, hoping to see a live demo. Maybe get some pointers on Firebase auth.
P.S. Even though I am good at following through documentation, with videos it’s much faster to orient myself and get a birds eye view of a concept faster!
Hi Dgraph Team, one question on GraphQL+ ; What are the current capabilities/future directions around control-flows, looping, turing completeness for the query language?