It seems Redis
can provide same functionality as achieved thru Gemfire
OQL
queries, but with much of code change using spring/-boot/Java. Any insights would be highly appreciated!
Storing Data - Gemfire
can store Parent Object and use OQL capability to query deeply nested objects, without doing anything different during storing. But in Redis
it has to be stored based on the querying needs. So if we are expecting a "find x in xList
" kind of capability; xList
has to be stored as Set/List separately other than saving Parent Object.
Querying Data - If we have to store custom Objects in Redis
, appropriate Serializers also have to be used, which also makes an instance of RedisTemplate bound to a DataType. In a huge codebase, where hundres of different objects needs to be stored and fetched, this doesn't appear to be highly maintainable.
Is this the only way to store/fetch every custom Object in Redis, when Queries are complex and integrated using spring-boot? RedisRepository
doesn't suit the bill for complex queries