Consider a general Backup mechanism. about archcolider HOT 2 CLOSED

Good point.
I think we can add a small section about this near the overall architecture diagram with concerns about a state persistence for different tools and cases.

For instance:

• we don't need to backup data for orders in MQ, as the client app should implement a timeout mechanism for sending requests and getting responses. If there is no confirmation about payment acceptance or rejection, a user should be notified and retry should be offered. So for MQ we can rely on the build-in persistence model for the service restart scenario.
• EventStore requires a backup mechanism as it vital information for the system. Projections do not require backup as they can be reconstructed from events in EventStore. But we can backup projections to speedup the recovery scenario.
• Report service requires backup mechanism.
• Kafka do not require and we can rely on a build-in mechanisms.

from archcolider.

I guess we will store images in AWS S3 service. If so then we could use AWS Glacier for backup.

from archcolider.