Hello! 1. They are usually ran as stand alone processes on the designated machines. You can probably convert them to windows services with some effort. 2. Client nodes are actually fully functional Ignite distributed topology nodes. You should start a single client per web application. use it for all Ignite operations. 3. Have you seen .Net examples? https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/examples
Regards, -- Ilya Kasnacheev ср, 28 авг. 2019 г. в 20:16, Sudhir Patil <[email protected]>: > > Hi All, >> >> We are planning to use Apache ignite for distributed cache for .Net core >> web application. >> I had gone through the basics of ignite. >> Any suggestions on implementation of ignite with below points?? >> 1. How/where to host server nodes? Eg separate web application / windows >> service. >> 2. Client nodes is nothing but main web application consuming cache from >> server nodes? >> 3. Any sample git repository for consuming ignite in .Net core?? >> >> Thanks, >> Sudhir >> > > > -- > Thanks & Regards, > Sudhir Patil, > +91 9881095647. >
