You’re proposing two technical solutions, but we’re not familiar with the (functional) problem you’re trying to solve.
- Why is the API accessed? Is it for querying data or for storing data?
- If it’s for storing data, does it put a message on the queue? If so, why does it need to query data?
- If it’s querying data, why would it not be allowed to query data? What is happening with the data that it’s not allowed to query it?
- For the future scenario, someone/something needs to be in control to start the process. Who is going to publish the signal and why is it going to send the signal?
- A saga could be used to automatically publish another message (signal?) after an x-amount of time to flip the bit back.
I’m not familiair with the scenario, but somehow it feels like there are alternative scenarios where data possibly can still be accessed and not flags or signals are needed.
If it’s too complex to explain, you can also email us at support@particular.net and we’ll see if we can get on a call. If you mention my name, we can also speak Dutch if you like. But we can also continue here if that suits you better.