[
https://issues.apache.org/jira/browse/IGNITE-23651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17903032#comment-17903032
]
Pavel Tupitsyn commented on IGNITE-23651:
-----------------------------------------
Merged to main:
[b6be0ce886608830d20c38e5beae3e0d05f56bac|https://github.com/apache/ignite-3/commit/b6be0ce886608830d20c38e5beae3e0d05f56bac]
[~gurustron] thank you!
> .NET: Thin 3.0: Add ServiceCollection extensions for DI integration
> -------------------------------------------------------------------
>
> Key: IGNITE-23651
> URL: https://issues.apache.org/jira/browse/IGNITE-23651
> Project: Ignite
> Issue Type: Improvement
> Components: platforms, thin client
> Reporter: Pavel Tupitsyn
> Assignee: Sergey Stronchinskiy
> Priority: Major
> Labels: .NET, ignite-3
> Fix For: 3.1
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> As a user, I want to integrate Ignite 3 .NET client into my ASP.NET and
> Hosted Service applications using standard dependency injection
> infrastructure (*IServiceCollection*).
> Currently, it is not clear how to do that properly:
> * *IgniteClient.StartAsync* is asynchronous, and DI factory methods must be
> synchronous - what to do?
> * Should I use Scoped or Singleton?
> As Ignite developers, we recommend using a single *IgniteClient* instance, or
> a pool of clients, but this requires non-trivial setup.
> We should provide an *IgniteClientPool* implementation, and
> *ServiceCollection* extension methods to make it easy for the users.
> Example: Postgres driver
> https://github.com/npgsql/npgsql/tree/main/src/Npgsql.DependencyInjection
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
