-
1. Re: About Infinispan instances
pmuir Jul 5, 2011 8:02 AM (in response to jkiper)1 of 1 people found this helpfulI think the best thing to do would be to use a Write-Behind cache (see https://docs.jboss.org/author/display/ISPN/Write-Through+And+Write-Behind+Caching)...
-
2. Re: About Infinispan instances
jkiper Jul 5, 2011 2:22 PM (in response to pmuir)So, the only way to have a consistent backup would be with synchronus cache... Am I right? Thinking on multiple nodes, with multiple disks, could this be possible without a database? I think that for certain types of applications where we need to restore the data to a specific point in time a database is practically a must?
-
3. Re: About Infinispan instances
sannegrinovero Jul 5, 2011 2:41 PM (in response to jkiper)1 of 1 people found this helpfulYes about the synchronous, as the APIs don't expose "in flight" operations nor expose access to the transaction logs, so you could use the async only if you would stop writing to Infinispan for "some time", to wait that all async store operations have been applied in proper order.
You don't need to use a database-backed cacheloader to store the data, but anything having some notion of "point in time restore" would do, right? some filesystems support such operations, of course a database seems a good fit and you could make good use of your dba skills.
For your use case I'd consider implementing your own cacheloader: the interface is very simple, and you could intercept the changes by configuring it as a sync cacheloader, do what you need with it, and then delegate to an async store; the hard part to remember is that no node as a complete overview of the global state - that might be the big difference when coming from a database experience, and is also the main reason for scalability
-
4. Re: About Infinispan instances
jkiper Jul 5, 2011 2:46 PM (in response to sannegrinovero)Of course.... But you also have for example DB2 pureScale for scalability in the midrange database world, or paralel sysplex when talking about mainframes...
-
5. Re: About Infinispan instances
jkiper Jul 5, 2011 5:05 PM (in response to jkiper)Please be aware i'm not against data grids or infinispan, i'm just trying to figure out some issues coming in mind about infinispan implementation.
-
6. Re: About Infinispan instances
manik Jul 8, 2011 7:34 AM (in response to jkiper)What about low-latency data access? Being in-memory, you get the benefit of fast lookup with Infinispan.
-
7. Re: About Infinispan instances
jkiper Jul 8, 2011 2:34 PM (in response to manik)Yes, I know... My question is about persistence and backup / restore operations. I've mentioned pureScale and others in the means of scalability.
And you have another options for low-latency data access like in memory databases, solid disks, etc.
There are "dark areas" for me about Infinispan... like locking, commit and rollback operations, etc. when you have a cluster and a transaction pass the boundaries of a node...
A lot of stuff that is common in the database world I don't see them implemented in Infinispan.
-
-
9. Re: About Infinispan instances
pmuir Jul 21, 2011 6:51 AM (in response to jkiper)I've marked this as assumed answered as this dicussion appears to have run it's course. Julian, if you have further questions, feel free to continue or start a new topic.