Data Bus

  • Architectural
  • Decoupling
About 3 min


Allows send of messages/events between components of an application without them needing to know about each other. They only need to know about the type of the message/event being sent.


Real world example

Say you have an app that enables online bookings and participation of events. You want the app to send notifications such as event advertisements to everyone who is an ordinary member of the community or organisation holding the events. However, you do not want to send such notifications like advertisements to the event administrators or organisers but you desire to send them and them only the time whenever a new advertisement is sent to all members of the community. The Data Bus enables you to selectively notify people of a community by type, whether it be ordinary community members or event administrators, by making their classes or components only accept messages of a certain type. Ultimately, there is no need for the components or classes of ordinary community members nor administrators to know anything about you in terms of the classes or components you are using to notify the entire community except for the need to know the type of the messages you are sending.

In plain words

Data Bus is a design pattern that is able to connect components of an application for communication simply and solely by the type of message or event that may be transferred.

Programmatic Example

Translating the online events app example above, we firstly have our Member interface and its implementations composed of MessageCollectorMember (the ordinary community members) and StatusMember (the event administrators or organisers).

public interface Member extends Consumer<DataType> {

  void accept(DataType event);

Then we have a databus to subscribe someone to be a member or unsubcribe, and also to publish an event so to notify every member in the community.

 public class DataBus {

  private static final DataBus INSTANCE = new DataBus();

  private final Set<Member> listeners = new HashSet<>();

  public static DataBus getInstance() {
    return INSTANCE;

   * Register a member with the data-bus to start receiving events.
   * @param member The member to register
  public void subscribe(final Member member) {


   * Deregister a member to stop receiving events.
   * @param member The member to deregister
  public void unsubscribe(final Member member) {

   * Publish and event to all members.
   * @param event The event
  public void publish(final DataType event) {

            listener -> listener.accept(event));

As you can see, the accept method is applied for each member under the publish method.

Hence, as shown below, the accept method can be used to check the type of message to be published and successfully send/handle that message if the accept method has an instance for that message. Otherwise, the accept method cannot as is for the case of the MessageCollectorMember (the ordinary community members) when the type of message being sent is StartingData or StoppingData (information on the time whenever a new advertisement is sent to all members).

public class MessageCollectorMember implements Member {

  private final String name;

  private final List<String> messages = new ArrayList<>();

  public MessageCollectorMember(String name) { = name;

  public void accept(final DataType data) {
    if (data instanceof MessageData) {
      handleEvent((MessageData) data);

However, the StatusMember(the event administrators or organisers) can accept such types of messages as

public class StatusMember implements Member {

  private final int id;

  private LocalDateTime started;

  private LocalDateTime stopped;
  public void accept(final DataType data) {
    if (data instanceof StartingData) {
      handleEvent((StartingData) data);
    } else if (data instanceof StoppingData) {
      handleEvent((StoppingData) data);

Thus, the data bus outputs as follows:

class App {

 public static void main(String[] args) {
   final var bus = DataBus.getInstance();
   bus.subscribe(new StatusMember(1));
   bus.subscribe(new StatusMember(2));
   final var foo = new MessageCollectorMember("Foo");
   final var bar = new MessageCollectorMember("Bar");


//02:33:57.627 [main] INFO com.iluwatar.databus.members.StatusMember - Receiver 2 sees application started at 2022-10-26T02:33:57.613529100

//02:33:57.633 [main] INFO com.iluwatar.databus.members.StatusMember - Receiver 1 sees application started at 2022-10-26T02:33:57.613529100

Evidently, due to MessageCollectorMembers only accepting messages of type MessageData and none of either StartingData nor StoppingData, the MessageCollectorMembers are prevented from seeing what the StatusMembers (the event administrators or organisers) are shown: information on the time whenever a new advertisement is sent to all members.

Class diagram

data bus pattern uml diagram
Data Bus pattern


Use Data Bus pattern when

  • you want your components to decide themselves which messages/events they want to receive
  • you want to have many-to-many communication
  • you want your components to know nothing about each other

Data Bus is similar to

  • Mediator pattern with Data Bus Members deciding for themselves if they want to accept any given message
  • Observer pattern but supporting many-to-many communication
  • Publish/Subscribe pattern with the Data Bus decoupling the publisher and the subscriber