; --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Correct-Way-to-Store-Data-tp13163p13187.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
As well, for companies that have a large number of tables (as does ours),
using a cache per table would probably not be ideal.
Best,
Rick
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Correct-Way-to-Store-Data-tp13163p13187.html
Sent from the Apache Ignite
Err, I meant "[...] a different memory policy for different classes", not
for "different products".
On Fri, May 26, 2017 at 6:00 PM, Matt wrote:
> I don't think that's correct.
>
> As far as I know, on Ignite it's fine to put more than one type on the
> same cache, because a cache is like a sche
I don't think that's correct.
As far as I know, on Ignite it's fine to put more than one type on the same
cache, because a cache is like a schema (in the relational db world) and
not a table. So for each type on a cache, a different table on H2 is
created. There's no need for additional logic to f
Hi Matt,
Ignite cache more or less corresponds to table from relational world.
As for caches number: Both ways are possible. In relational world, by the
way, you also can place different business objects into one table, but you
will have to introduce additional type field.
Similar for the
Interesting, so #3 is not the way to go.
What about #2? That would be the "relational database way of doing it",
which is what Ignite uses behind the scene (H2). What's the disadvantage
compared to #1?
Thanks for sharing your insight.
On Fri, May 26, 2017 at 11:28 AM, Ilya Lantukh
wrote:
> Hi
Hi Matt,
>From what I've seen, the most commonly used approach is the one you took:
have caches associated with object classes. This approach is efficient and
completely corresponds to "the Ignite way".
Having a separate cache for each product is definitely not a good idea,
especially if you have
Hello,
Right now I have a couple of caches associated with the kind of objects I
store. For instance I have one cache for products, one for sales, one for
stats, etc. I use the id of the product as the affinity key in all cases.
Some questions I have regarding this approach...
*1.* I get the imp