|
Hey Mark Paluch, thanks for grabbing that one! Musing a bit more about association handling, I came to think that Redis lists seem a good fit, with the owner id and association role represented within the list key:
Customer:123:orders -> 456,789,...
That's probably how I'd model it when having the need for it in Redis, also when leaving OGM out of the picture.
For referenced composite keys the same JSON representation also used for hash keys could be used:
Customer:123:orders -> {"type":"B2B","seq":"456"},{"type":"B2B","seq":"789"},...
That's not as nice, but composite keys are just going to be not great with this type of store anyways.
WDYT?
|