batuhan
commented
2 years ago Closing this.
My current approach is to keep these in simple containers in a Kubernetes cluster (or in a mid-tier instance w/ docker-compose) and see how and how much we utilize the underlying features elasticsearch gives us to see if replacing it makes sense.
If we are gonna use AWS, their ES-compatible serverless services might be enough. Too lazy to Google the name of that.
We currently use ElasticSearch for querying (list methods on the API) and data generation. PostgreSQL is awesome and we should move these to PGSQL to have one less dependency.
This is not a priority as it costs more to remove it than it costs to run ES on some cloud.
I should also note we use Elastic APM for performance metrics and logs on core so unless we want to make New Relic richer we might wanna keep it too