With removal of 'type' in mapping from 6.x release, On Dynamic Application Development Platform Project, I required many indices need to be created. All Indices have documents which don't have many similarities.
Form of Application-1
Field - A (String)
Field - B (int)
Field - C (Date)
Form of Application - 2
Field - X (int)
Field - Y (int)
Field - Z (long)
There are as many as 50 Application per Tenant. It can scale up to 500 Tenant. So, Selected design approach can have 500 X 50 = 25000 Indices. However, Each indices/application might be very small memory size (i.e. KBs to Couple of MBs at Max)
I read the forum and it has been mostly suggested to keep dense data in minimum number of indices. But in my case, There are many models without no overlapping fields. So, I do see one option which is index per model (i.e. form of application in my use case)
My question : is it good design approach considering use case ? or better alternatives ?