Do you think we should make the transaction service a singleton? This means that we would be able to call the same transaction from the service container from event listeners and controllers and it would be the same instance, allowing us to potentially create big transactions. I don't know if this might have some weird implications if we were to implement it now, where there may be multiple instances of the transaction at any one time, causing the wrong transactions to be committed or something.
Do you think we should make the transaction service a singleton? This means that we would be able to call the same transaction from the service container from event listeners and controllers and it would be the same instance, allowing us to potentially create big transactions. I don't know if this might have some weird implications if we were to implement it now, where there may be multiple instances of the transaction at any one time, causing the wrong transactions to be committed or something.