This feature would be critical for our infrastructure. We have two different applications working on sensor data, both of which support offline functionality. As a result, we must maintain three separate databases, two of which are typically beyond our control.
The only reliable way to manage time series data and ensure full synchronization between databases would be to use change streams or, as we are doing right now, periodically query the entire database for marked unsynchronized data when we have connection to the database server. However, this approach is not only incredibly slow but also resource-intensive for both the data and the infrastructure we currently have.
We will periodically monitor the status of this feature request as we aim to migrate our infrastructure to MongoDB Atlas and streamline the development of our application.
This feature would be critical for our infrastructure. We have two different applications working on sensor data, both of which support offline functionality. As a result, we must maintain three separate databases, two of which are typically beyond our control.
The only reliable way to manage time series data and ensure full synchronization between databases would be to use change streams or, as we are doing right now, periodically query the entire database for marked unsynchronized data when we have connection to the database server. However, this approach is not only incredibly slow but also resource-intensive for both the data and the infrastructure we currently have.
We will periodically monitor the status of this feature request as we aim to migrate our infrastructure to MongoDB Atlas and streamline the development of our application.
Thank you in advance