Data Ingest is a sync strategy for applications with heavy client-side insert-only workloads. You can enable it for one or more collections. It supports writing to any collection type, including an Atlas time-series collection.
For example, an IoT app that frequently logs sensor data has a significant write workload and no read workload. The device may also be offline for extended periods of time. Data Ingest bypasses some of the processing required for bi-directional sync, significantly improving write speed to an Atlas collection.
It sounds like you just want to run a push replication on top of your data set instead of the default push/pull.
What @borrrden said but more generally speaking from an arch standpoint, you should consider if you need all the IoT app data to be pushed up to the cloud. Most of the time, the sensor data is temporal in nature and does not have to be persisted. For that, deploying a hierarchical topology by doing local sensor processing locally at the edge and then filtering out for aggregating the data before pushing up to cloud would be more scalable option.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.