Redis7 for caching/event

[trydofor]

First, replace Redis with Hazelcast in the following situation

Driving

• Simplicity - redis needs to be deployed, while hazelcast is embedded
• Serialization compatibility - redis has no nearcache, there is some serialization compatibility

Restraining

• Widely used - redis is much more widely used than Hazelcast
• Cloud services - redis is used as a basic service.

Scenarios

• spring session - spring integration
• Distributed caching - major business scenario
• Global lock - global business lock, not required to be distributed, can be centralized locking
• Pub/Sub - simple messaging service
• flakeId - non-essential feature

History

• redisson - this scenario
• Removed commits - a1409a1

[trydofor]

• Separate hazelcast as optional dependency
• Provide redisson or redis modules