Wayne, You can stick huge items into ignite as a value of a key store. Have seen design patterns whereas a queueish structure was thrown in as a value corresponding to a key, and clients of queue retrieved the queue by the key, then queued data in/out.
Not a high speed solution. What is your access pattern of the large object? That is the guiding principle if this is a good idea. SCott -----Original Message----- From: wt <[email protected]> Sent: Friday, March 29, 2019 8:36 AM To: [email protected] Subject: key value cache - value size limits or concerns Is the following design appropriate or does it need reworking i want to build a key value store where the key is a company and the value is a list of data that will grow over time. The value data can contain thousands of items and these can change over time. My question is having a value for a given key of this size a problem that might be realised down the road or can ignite handle large growing values? Alternatively i guess i would need to design a more granular set but then the key is the issue as it will need to include info that might be hard for users to use. Regards Wayne -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
