Currently, dafda is a single repository that contains multiple solutions, including examples, etc.
We could consider splitting it up a little. Do we still need to maintain things like Academia?
Moreover, we could split the pacakge a little, where instead of (Consuming, Producing, Outbox), this could be 3 separate, smaller packages.
Only a fraction of users use the actual Outbox infrastructure. In a same manner, there are use cases where the pacakge is used only for producing or consuming flows...
Currently, dafda is a single repository that contains multiple solutions, including examples, etc.
We could consider splitting it up a little. Do we still need to maintain things like Academia?
Moreover, we could split the pacakge a little, where instead of (Consuming, Producing, Outbox), this could be 3 separate, smaller packages.
Only a fraction of users use the actual Outbox infrastructure. In a same manner, there are use cases where the pacakge is used only for producing or consuming flows...