I think we as a community need to determine what value do we want to add with the Redis adapter. Redis already does a great job storing small data structures in memory and sharding them. We do a great job of making sure that these data structures are horizontally scalable; why would we want to replicate what another open source project is already implementing?
Having said that, I would like to see a configuration property that lets the user chose between a single server vs a distributed collection. > I think we could have the following options: > > 1. have a property that could be set to use either single server > collections over use the current distributed collection > 2. have first class collection implementations that are distributed by > nature, as using key:value as the hammer for all does not make sense > I don't think these options are mutually exclusive. We should make lists and SortedSets first class data structures in Geode alongside regions.
