Hello, Feel free to use Ignite .NET for that. Moreover, you have 2 options here:
1. Use .NET standard client (supports most of the APIs but connects to the cluster via a JVM process started internally). Here is how you can define its config for entries eviction: https://apacheignite-net.readme.io/docs/eviction-policies 2. Use .NET thin client (lightweight, connects via a proxy server - not that fast but will be addressed in next releases and doesn't start the JVM): https://apacheignite-net.readme.io/docs/thin-client Btw, keep in mind that SQL engine requires all the data to be in Ignite cluster - it won't go to SQL Server if anything is missing in RAM. Our SQL engine can go to disk only if native persistence is enabled. - Denis On Tue, Apr 9, 2019 at 6:57 AM Asadikhan <ak...@cleverdevices.com> wrote: > I want to setup a basic Ignite cluster to start playing around with. What I > am trying to achieve is setup 3 VMs in Azure that will make up the Ignite > Cluster. On the back-end I want to use either SQL (for my POC) which I will > later replace with Cassandra (for POC again - I think SQL would be easier > to > start with given my knowledge). > > The key thing I want to achieve is use Ignite as a write through cache. So > if I ingest 1TB of data, I want to retain say most recent 100GB of that in > Ignite while the rest of the it passes through to the backing SQL Server. > > I am more familiar with .net but I can use Java too if needed. Should I use > Apache Ignite.net for this or Apache Ignite. Also, can someone either point > me to resources/documentation or give me a high level breakdown of what I > need to do to achieve this? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
