go-eventbus is a library of publish/subscribe event bus for Golang, inspired by EventBus

go-eventbus targets on decouple. Go language already ensure a good performance.

• Inverse of control (aka. Dependency injection)

• EventBus

Components doesn't rely on each other. They publish events to EventBus, and retrieve interested event from that too.

• Actor model

Component call others by name. Controller hold name <--> components mapping. Then it's possible to use different components in different env for same name

As you can see, go-eventbus is designed for event based system. Normally, for event based system, workflow is like:

1. Something happened: event generated
2. Some component, like A do something to respond the event (eg. when user click a url, open a website tab)
3. After that, A wait for another event to come

Instead of calling: http.post(xxx)

Consider using EventBus: bus.Request(HttpPostEvent).GetResult()

HttpPostEvent is responded by another component. It could made a real HTTP call in PRD, or it could return directly by a mocked component. All that depends on what components are attached to the bus.

• 1 response to each event: 50000~100000 event dispatch per sec
• 5 responses to each event: 20000 event dispatch per sec
• It's not ideal, performance is still improving