Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using Bolt Client vs GraphClient #426

Open
mcalvin-kinectify opened this issue Oct 12, 2021 · 1 comment
Open

Using Bolt Client vs GraphClient #426

mcalvin-kinectify opened this issue Oct 12, 2021 · 1 comment

Comments

@mcalvin-kinectify
Copy link

Hello,
I am trying to use the configuration described in the documentation that allows you to create a new graph client inside my scoped method using the IGraphClientFactory. However, because I have a relatively high volume of transactions flowing through my system at once (sometimes 100K+), I wanted to use the Bolt client instead of the http based Graph client. Is this possible? Here is what I am registering in my IOC Container:

  services.AddSingleton(context =>
  {
      

      return NeoServerConfiguration.GetConfigurationAsync(
          new Uri(path),
          config.GetValue<string>("Neo4j:User"),
          config.GetValue<string>("Neo4j:Password")
      ).GetAwaiter().GetResult();
  });

It seems like you can only use http(s) with the Uri object though, so if I pass something like: neo4j://some-path.to.svc or bolt://some-path.to.svc I get an error message. I didn't see any overload of the NeoServerConfiguration.GetConfigurationAsync method that takes something other than a Uri though.

Also, since my team is using this library, we would love to dedicate some time to helping support it. Please let me know if you are interested in any help.

@cskardon
Copy link
Member

Hello!

Hmm, well, not with the existing IGraphClientFactory - it's all HTTP I'm afraid.
I would be totally fine with PRs bringing in parity between the two with things like this - and the offer of support is welcome - largely at the moment it will revolve around doing PRs and pulling them in, if you find issues - things you want fixed I'm always happy to look at them

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants