My company is currently working on migration away from Amazon CloudSearch (ACS) to Elastic.
ACS Domains are basically a single index, unlike ES which as I've learned can support virtually unlimited numbers of distinct indices (each with their own fields etc). Please correct me if I'm wrong.
Currently we have many ACS domains which are relatively very expensive for the usage they receive (on the order of < 10k requests per day). I would like to be able to combine a few (or all) of those domains into one Elastic Cloud instance to save $$ and optimize usage... no sense over-provisioning these for the low usage they receive.
One of my developers is telling me this is a bad practice, that separate indexes have more overhead/slower speeds. Is this accurate?
Assuming the underlying Elastic Cloud cluster is provisioned well, would my approach of mapping each unique ACS domain to their own ES index work?