What's the preferred way to manage Cloud Storage and Datastore connection objects in ASP.NET?

I’ve been using the Datastore and the Cloud Storage in an ASP.NET (Core) application, and I’m wondering what’s the preferred way to manage DatastoreDb and StorageClient instances.

Currently I’m creating a new instance on every request. Is there any more sophisticated support in the library to manage the connection objects, for example some kind of pool?

Thanks!

(Is this the proper place to ask questions like this, or should I rather post it to SO?)

[jskeet]

@philipri: Right - that definitely explains it, as if you were constructing a new channel on each request, that would mean a new connection.

What you’re doing is indeed fine. In production I’d expect you to be able to use DatastoreDb.Create() specifying just the namespace on each request - as that would use the default app credentials, it could keep a single channel open for all requests. That difference between local testing and production may be harder than just keeping a singleton client in both cases though. So long as there’s nothing I don’t understand, I think we’re fine 😃

As an aside, if you have any usability feedback on the DatastoreDb API, now would be an ideal time to give it while the surface is still somewhat malleable.

[jskeet]

@philipri: When did you try this, out of interest? For Datastore and other gRPC-based APIs, “fairly recent” versions of the package will all share a common Channel if you’re using default application credentials. You definitely shouldn’t be seeing that issue.

When you say the tests were “on the local store” - if that means you were creating a new channel to the local emulator each time, that would explain it. You could keep just the channel as a singleton and reconstruct the rest… but basically if you need a new connection on each request, that will be slow. You could also use the ChannelPool class in GAX to avoid having to create a new Channel each time. (That’s slightly cleaner than keeping a static reference to the channel, although I admit there’s not a lot in it.)