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 <[email protected]> wrote: > 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)Thin clients (ODBC/JDBC) - you may store the connection open but it could > be closed. So you can try to use some connection pull. > > https://apacheignite.readme.io/docs/thin-clients > > 2)REST - just open the connection and do some operations. Also could be > timed out. So you could open a new connection for every update. > > BR, > Andrei > > https://apacheignite.readme.io/docs/rest-api > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
