amazon-sqs-java-messaging-lib VS Redis

Save to SQS (i.e. save each Event to Amazon’s SQS queuing service)

Amazon SQS

Messaging/Queueing Systems (Amazon SQS, RabbitMQ, Beanstalkd)

The last stage is productionizing the model. The goal of this phase is to create a system to process each image/video, gather the relevant features and inputs to the models, integrate the models into a hosting service, and relay the corresponding model predictions to downstream consumers like the MCF system. We used an existing Safety service, Content Classification Service, to implement the aforementioned system and added two specialized queues for our processing and various service integrations. To use the model for online, synchronous inference, we added it to Gazette, Reddit’s internal ML inference service. Once all the components were up and running, our final step was to run A/B tests on Reddit to understand the live impact on areas like user engagement before finalizing the entire detection system.

One of the challenges Redis labs here have is that there's very little reason for their userbase to stay loyal to them.

antirez retired from Redis development a few years ago.

From https://github.com/redis/redis/graphs/contributors it looks like activity since he left has been mostly from people who didn't overlap with him much.

Redis Labs have not shown themselves to be outstanding stewards of the project as far as I can tell. Why shouldn't people support the fork?

Redis

Redis - real time data storage with different data structures in a cache

[0] https://github.com/redis/redis/blob/unstable/CONTRIBUTING.md

Cache: a Redis cache