Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 1
    Do you want to synchronize, backup, or archive the data? Each option would use different approaches. Is the clound database multi tenant? Does the cloud database also require processing, querying etc? Is the data ever changed after it has been added? Commented Dec 10, 2024 at 12:56
  • This is an archive setup I would say. The data on the cloud is query only, and will recieve considerable query traffic. The only write modification to the cloud database is done when a backup/archive event is done, and that can be guarranteed to be done by only one user, one at a time. Commented Dec 10, 2024 at 18:49
  • 2
    Databases should not be identical. There should be an API that accepts data, verifies it, transforms and pushes to the remote database. There are multiple benefits of that. Like for example you can run different client versions, with different data format and still have unified database on the other side. Commented Dec 10, 2024 at 20:04
  • I think the word 'synchronize' is incorrect here. That doesn't align with what you are describing. If they were synchronized, you would have the same data in both databases. You should probably read some articles on the CAP Theorem as well, if you are not already familiar with the idea. Commented Dec 16, 2024 at 18:55