Provide higher-level client and make a pool an aggregation of them #34

New issue

Open

opened 2023-03-08 23:37:52 +00:00 by snegurochka · 0 comments

snegurochka commented

2023-03-08 23:37:52 +00:00

Member

Original issue: https://github.com/nspcc-dev/neofs-sdk-go/issues/380

Currently pools solve several problems at once:

hide a set of clients behind one pool instance and balance requests between them
provide higher-level API

Granted, in some ways pool code had to do the second just to use the same client for a set of related operations, so pools can't provide raw client.Client interface (at least not in a usable way). But at the same time this API simplifies some operations and regular single-client users might benefit from it as well (see #345 also, it's related to building a higher-level client).

So the proposal here is to add some higher-level client that will provide some pool-alike (+ #345) interface and then make pool be just an aggregation of these clients (with the same interface).

Original issue: https://github.com/nspcc-dev/neofs-sdk-go/issues/380 Currently pools solve several problems at once: * hide a set of clients behind one pool instance and balance requests between them * provide higher-level API Granted, in some ways pool code had to do the second just to use the same client for a set of related operations, so pools can't provide raw `client.Client` interface (at least not in a usable way). But at the same time this API simplifies some operations and regular single-client users might benefit from it as well (see #345 also, it's related to building a higher-level client). So the proposal here is to add some higher-level client that will provide some pool-alike (+ #345) interface and then make pool be just an aggregation of these clients (with the same interface).