3 ms·
2.2k/mo right off the bat is pretty steep, especially if you're paying that while the search response reliably takes over 10 seconds. Why would you shovel 1.5k
by ljm 3y ago
2.2k/mo right off the bat is pretty steep, especially if you're paying that while the search response reliably takes over 10 seconds.
Why would you shovel 1.5k into MongoDB's pockets right off the bat? Especially when ElasticSearch is much better suited to what you're trying to do?
- dinobones 3y agoYou could run this entire stack (yes, even for 25 million products) using Kubernetes in a $40/month Linode + Elasticsearch + Cloudflare free plan.
- altdataseller 3y agoSounds like someone drank the Mongo kool-aid. You absolutely do not need Mongo, let alone Mongo Atlas. 25 million documents with ecommeece products is measly and should fit in a single 600 GB server
- ljm 3y agoProbably not even that - 25mil is nothing really. A normalised schema in an RDBMS would handle that without sweating.