to aid in creating de-coupling libraries and applications. So far in my go journey, although I have strived to write de-coupled code, the end result is more coupled then I would like, so a new appraoch has to be taken. I just discovered this bus which looks like it can help.
bus has more feature than I require. I want it to be as simple as I need it to be with no extraneous functionality. It was designed to be used in an async context so it uses locks internally. I only need this to work on a synchronous basis so I don't want the overhead of acquiring and releasing locks.
Also see:
to aid in creating de-coupling libraries and applications. So far in my go journey, although I have strived to write de-coupled code, the end result is more coupled then I would like, so a new appraoch has to be taken. I just discovered this bus which looks like it can help.
bus has more feature than I require. I want it to be as simple as I need it to be with no extraneous functionality. It was designed to be used in an async context so it uses locks internally. I only need this to work on a synchronous basis so I don't want the overhead of acquiring and releasing locks.
Also see: