Why not using Redis instead of ES for internal engine?

Hello Kuzzle Team 😃,

I’m wondering if the internal index %kuzzle has its place in ES. I mean, Plugins, Services, etc are only used by Kuzzle for internal usages. We don’t need to perform complex searches on this index. The only use case (tell me if I’m wrong) is to get the configuration by key and that’s it. Maybe it’s about replication? But I guess we can also use the Redis replication for let all Kuzzle know about new services, or plugins configurations.

I have the feeling that we’re decoupling (yes, a very tiny little bit) Kuzzle from ES if internalEngine is working with Redis. And if we think about it, it’s weird to store internal configuration inside a search engine.

I’m not at this office for putting a post-it on the window, so I let an issue instead 😃. We could talk about it when I’m back.

See you soon team.

[j33f]

it depends on the goal: if the goal is to be agnostic from the data storage, using something like pouch or sqlite could be an option… so the question is: why storing all we are storing into %kuzzle currently in ES elsewhere ?

[scottinet]

Outdated concerns