Project demonstrating a concept for delta sync between different applications
-
There are pull requests underway to deal with misordering of delta messages, which needs support in mu-authorization, delta-notifier and the producer.
-
Effective inserts and deletes could be useful and are also underway in mu-auth and the delta-notifier.
Keys are intentionally omitted from the configuration directories. Read the mu-tunnel documentation for instructions on creating the necessary keys.
First, start the producer using
docker-compose -f docker-compose.yml -f docker-compose.producer.yml -p producer up -d
Alternatively, the producer may be started including a stress-testing "timer" service. This can be done by including the docker-compose.timer.yml file:
docker-compose -f docker-compose.yml -f docker-compose.producer.yml -f docker-compose.timer.yml -p producer up -d
Then, start the consumer using
docker-compose -f docker-compose.yml -f docker-compose.consumer.yml -p consumer up -d
The producer is accessible at localhost:81 and the consumer at localhost:82.
The container_name key is used in the Compose files, so it is not possible to start multiple producers or consumers currently. However, if the appropriate container names were changed and configured, multiple consumers should work.