Replied on StackOverflow
https://stackoverflow.com/questions/53842387/scoped-vs-singleton-ignite-client-node-in-net-web-api/
In short, use Singleton, because "Thick" client is heavy and thread-safe.
On Wed, Dec 19, 2018 at 5:28 PM aealexsandrov
wrote:
> Hi,
>
> Generally
Hi,
Generally, you should have a working Ignite cluster somewhere that will
store and process your requests.
I am not sure that you really require the client node in your case. It will
use additional memory and CPU.
You can use several ways to work with Ignite cluster without fat client
node:
1
I am try planning to introduce Apache Ignite into existing old .net web api
project to use it as key/value store for detecting duplicate requests sent
to the load balanced api.
I would like to introduce minimum overhead to each request.
As I understand Client node is communicating to the server t
