I agree, and this has been on my list for a while, but never got to it. We need a "real world" showcase, like some e-commerce website built entirely with Ignite.
On Fri, Aug 30, 2019 at 5:43 PM Alexandr Shapkin <lexw...@gmail.com> wrote: > Meanwhile, I think it’s true that we are lacking of complete .NET examples > for modern apps. > > It would be perfect if anyone would share their Ignite .NET experience so > that we could collect them in a single place. > > > > Incidentally, Pavel’s GitHub page is a good starting point. > > > > > > *From: *Pavel Tupitsyn <ptupit...@apache.org> > *Sent: *Friday, August 30, 2019 5:34 PM > *To: *user@ignite.apache.org > *Subject: *Re: Apache Ignite distributed cache for .Net core web app > > > > Consuming Ignite in .NET Core is not really different from classic .NET. > > > > As for web application usage, there are many scenarios, I can suggest any > of the following: > > > > 1) Start Ignite Server node right in your web app > > Pros: > > - Simplest development and deployment > > - Best performance in cases of small deployments > > Cons: > > - Slow web app startup, increased resource usage on single machine/process > > > > 2) Start standalone Ignite nodes either on a separate cluster or on every > server with web app, connect from web app with Thin Client > > Pros: > > - Fast web app startup > > - Web app process is dedicated to serving web requests and does not share > resources with Ignite, can be faster in large deployments with high load > > Cons: > > - Thin Client API is less capable than "thick" in-process mode > > > > > > On Fri, Aug 30, 2019 at 5:19 PM Ilya Kasnacheev <ilya.kasnach...@gmail.com> > wrote: > > Hello! > > > > The link that I have provided has dotnetcore/ dir which hopefully contains > those. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > пт, 30 авг. 2019 г. в 17:06, Sudhir Patil <patilsudhi...@gmail.com>: > > Thanks Ilya, yes I had gone through those git samples. > > I was asking if any other repo for .Net core. > > > > Regards > > Sudhir > > On Thursday, August 29, 2019, Ilya Kasnacheev <ilya.kasnach...@gmail.com> > wrote: > > 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 <patilsudhi...@gmail.com>: > > > > 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. > > > > -- > Thanks & Regards, > Sudhir Patil, > +91 9881095647. > > >
