See if you can change the order_clothing.rs processor to forward the DaaSDocument to another topic, (e.g.: billing) after it finished its data provisioning.
Try to create a second data provisioning microservice, (e.g.: order_clothing_products that collects a list of unique products ordered) and listens to the same order.clothing topic.
Try implementing the PbD Data Usage Agreement in one of the provisioning microservices so that it only processes data that has an agreement for marketing purposes.
- Postman Helper - Command line utility to assist in the building of Postman collections for testing your DaaS services