Best Distributed Cache for Keeping Accesing configuration data<10 GB and access it for each record from a Flink streaming application?

Question

I have data that is not going to be more than 10 GB , and i need to put it in Distributed Cache and access it for each record for validation from my Flink streaming application. Which one is best for this use case? i am confused between hazelcast and redis.

Answer 1

The obvious solution would be to keep this data in Flink state, rather than in some external system.

To update the data, stream in new versions from any of the data sources supported by Flink, such as a filesystem or message queue.