I've decided to write a blog post, since this topic seems to be in demand: https://ptupitsyn.github.io/Ado-Net-Cache-Store/
Code: https://github.com/ptupitsyn/ignite-net-examples/tree/master/AdoNetCacheStore Let me know if this helps! On Fri, May 26, 2017 at 3:50 PM, Chetan D <ccheta...@gmail.com> wrote: > Thank you Pavel. > > waiting for your response. > > On Fri, May 26, 2017 at 6:03 PM, Pavel Tupitsyn <ptupit...@apache.org> > wrote: > >> To give everyone context, this is not about GridGain, but about Apache >> Ignite. >> The blog post in question is https://ptupitsyn.github.io >> /Entity-Framework-Cache-Store/ >> >> Chetan, I'll prepare an example with Ignite 2.0 / ado.net and post it >> some time later. >> >> Pavel >> >> On Fri, May 26, 2017 at 2:32 PM, Chetan D <ccheta...@gmail.com> wrote: >> >>> ++ User List >>> >>> any help much appreciated. >>> >>> Thanks And Regards >>> Chetan D >>> ---------- Forwarded message ---------- >>> From: Pavel Tupitsyn <ptupit...@apache.org> >>> Date: Fri, May 26, 2017 at 4:38 PM >>> Subject: Re: Write behind using Grid Gain >>> To: Chetan D <ccheta...@gmail.com> >>> >>> >>> Hi Chetan, can you please write this to our user list, >>> user@ignite.apache.org? >>> So that entire community can participate. >>> >>> Thanks, >>> Pavel >>> >>> On Fri, May 26, 2017 at 1:35 PM, Chetan D <ccheta...@gmail.com> wrote: >>> >>>> Hi Pavel Tupitsyn, >>>> >>>> I have posted a comment in your blog as well (entity framework as >>>> ignite .net store) regarding write behind using ignite. >>>> >>>> I have been working on a project where i need to implement distributed >>>> caching and i have been asked to look into grid gain. >>>> >>>> This is is the first time i am working on caching and this is entirely >>>> new topic for me. >>>> >>>> The example which you have shared i was able to understand a little and >>>> the sad part is even entity framework also i have never worked on. >>>> >>>> It would be helpful if you can share me a simple example using ado.net >>>> implementing read through, write through and write behind even a simple >>>> table helps me understand the concept. >>>> >>>> >>>> >>>> >>> >>> >>> >>> >> >
