Splitting apps data in multiple stores vs single store - any practical advice, real life expirience?

[hrstoyanov]

Hi, I am trying to decide whether I should split my app data:

• orders (core biz data)
• audit events
• users management (authentication and authorization)
  into 3 separate ES stores, or just keep them in one.

Has any one "been there, done that, here are my scars" willing to share some wisdom? For example - what are the performance implications (channels count), back-up implications, etc.

[Flo9520]

We had our application set up as 1 storage per service. In the end we switched to a storage for hot data (users, configuration, etc) and a storage for cold data like events.
Performance wise we had no issue at all and the whole backup and restore process is also easier since there is less work to do. The only worry I have is when the data gets corrupted you lose everything instead of just some partial data but let's just pray this never happens.

[hrstoyanov]

Thanks. I am cinsidering splitting my data as 3 separate storages:

• user security (authentication data, authorization - groups and roles, etc)
• core app data (orders, products, etc.)
• audit events - this will grow over time, but I will implement some "garbage collection" thread to truncate it