@drq

Yes, there likely is; however I am not sure I can answer this because the question is missing the topology - which you LIKELY defined in your docker compose file.

Unless you DIDN'T and this is "across multiple machines running the same docker-compose item" - again, not sure of the topology.

So essentially your question is "what is the best practice for synching data between backend services." Apply those practices to your idea.

Docker is, you know, just one way to deal with writing service topology and infrastructure codified.

(I might suggest using a distributed filesystem, maybe gluster or something like that. However I haven't had to do this recently despite having a project that really needed it, because that portion of the project was overengineered and we solved the issue by NOT OVERENGINEERING IT, eliminating the need for 6 unsynched backends instead of a single central data store)