1 Answer
- Newest
- Most votes
- Most comments
0
Any queries on MemoryDB using the JSON interface is done through filtering (Similar to like operator in a database) - Since all the data is in-memory (RAM) - the additional overhead on compute for searching/sorting through the data is not very significant - (maybe a 10% - 20% overhead in compute - this number will vary based on the details of the use-case). If you compare the cost of this overhead to the cost of additional storage if you were to create indexes on this data - you are better off provisioning a bit more compute and using the querying capabilities of JSON instead of using a full fledged search module. This is not the case for every customer - I suggest you engage a specialist SA to look into the customer's ask.
answered 2 years ago
Relevant content
- Accepted Answerasked a month ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago