7 ms·
There is a discussion on Reddit for a 5TB data volume but very low throughput, I think Object Storage based document database would help in this case. https://
by fluxkernel 11mo ago
There is a discussion on Reddit for a 5TB data volume but very low throughput, I think Object Storage based document database would help in this case.
https://www.reddit.com/r/mongodb/comments/1o41dta/is_there_a_large_data_low_throughput_plan_for/ https://www.reddit.com/r/mongodb/comments/1o41dta/is_there_a...
- hodr_super 11mo agoMongo Atlas also supports using archive database to store infrequently accessed cold data. It’s also object storage based.
- fluxkernel 11mo agoTypically a separate archive database is not desired choice. You need to specify the rule how old the data is move from production database to archive database. Also the archive database is read only and slow, you can not achieve transaction between production database and archive database.
- iamlintaoz 11mo agoYes, this is exactly the typical use case where EloqDoc shines. Our auto-tiering feature allows you to manage a massive database (e.g., 5TB+) primarily on cheap, durable object storage (like S3), which is already built for cross-AZ replication and is up to 3x cheaper than traditional cloud block storage (EBS). We use local NVMe SSDs (200K+ IOPS) purely as a high-performance cache layer to accelerate read access. Hot and cold data are automatically swapped across memory, SSD, and object storage tiers based on access frequency, ensuring high performance (up to 100x faster than archive solutions)