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 through TCP. My current go to plan is to create a singleton object which will establish connection to the remote cache and register it in my DI container. Is it ok to leave node running and TCP connection open or should make the ignite object scoped to start close on each request/response cycle? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
