Synchronizing data to Redis without intermediate database table

mikko.ropanen

https://docs.spryker.com/docs/scos/dev/back-end-development/data-manipulation/data-publishing/handle-data-with-publish-and-synchronization.html#storage-table mentions:
"To synchronize data with Redis, an intermediate Zed database table is required."

But… is it? I'm sure there is a way to directly queue stuff in a sync.storage.* queue, but haven't quite figured it out yet.

The use case I have is that I need to store just a mapping between a product attribute value and another thing in Redis, and it doesn't make sense to me to create a *_storage table just for this.

Originally I just used the default product_concrete storage but inactive products are not stored in Redis, and I need those.

Alberto Reyer

You could adapt the publishing writer of your entity to immediately put the data into the related sync queue.
The sync behavior of propel ( https://github.com/spryker/synchronization-behavior/blob/1.8.0/src/Spryker/Zed/SynchronizationBehavior/Persistence/Propel/Behavior/SynchronizationBehavior.php ) would be a good place to look on how to sync into the storage queue.

But there is a reason for the intermediate store/page_search tables. If you ever have a data loss in the storage or search you want to restore the data as fast as possible.
If you need to recalculate the data (publishing) it will normally take significantly longer then just synchronizing into the storage or search (synchronization)