docs: update data bus

data-bus/README.md

@@ -1,22 +1,28 @@
 ---
 title: Data Bus
-category: Architectural
+category: Behavioral
 language: en
 tag:
     - Decoupling
+    - Event-driven
+    - Messaging
+    - Publish/subscribe
 ---
 
+## Also known as
+
+* Event Bus
+* Message Bus
+
 ## Intent
 
-Allows send of messages/events between components of an application
+The Data Bus design pattern aims to provide a centralized communication channel through which various components of a system can exchange data without being directly connected, thus promoting loose coupling and enhancing scalability and maintainability.
-without them needing to know about each other. They only need to know
-about the type of the message/event being sent.
 
 ## Explanation
 
 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.
+> 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
 
@@ -33,7 +39,7 @@ public interface Member extends Consumer<DataType> {
 }
 ```
 
-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.
+Then we have a data bus to subscribe someone to be a member or unsubscribe, and also to publish an event so to notify every member in the community.
 
 ```java
  public class DataBus {
@@ -100,6 +106,7 @@ public class MessageCollectorMember implements Member {
             handleEvent((MessageData) data);
         }
     }
+}
 ```
 
 However, the StatusMember(the event administrators or organisers) can accept such types of messages as
@@ -112,6 +119,7 @@ public class StatusMember implements Member {
     private LocalDateTime started;
 
     private LocalDateTime stopped;
+
     @Override
     public void accept(final DataType data) {
         if (data instanceof StartingData) {
@@ -120,10 +128,10 @@ public class StatusMember implements Member {
             handleEvent((StoppingData) data);
         }
     }
+}
 ```
 
-
+Here is the App class to demonstrate the Data Bus pattern in action:
-Thus, the data bus outputs as follows:
 
  ```java
  class App {
@@ -136,29 +144,59 @@ Thus, the data bus outputs as follows:
         final var bar = new MessageCollectorMember("Bar");
         bus.subscribe(foo);
         bus.publish(StartingData.of(LocalDateTime.now()));
+    }
+}
  ```
 
-//OUTPUT:
+Thus, the data bus outputs as follows:
 
+```
 //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](./etc/data-bus.urm.png "Data Bus pattern")
 
 ## Applicability
-Use Data Bus pattern when
 
-* you want your components to decide themselves which messages/events they want to receive
+* When multiple components need to share data or events but direct coupling is undesirable.
-* you want to have many-to-many communication
+* In complex systems where the flow of information varies dynamically.
-* you want your components to know nothing about each other
+* In distributed systems where components might be deployed across different environments.
+
+## Known Uses
+
+* Event handling systems in large-scale applications.
+* Microservices architectures for inter-service communication.
+* Real-time data processing systems, such as stock trading platforms.
+* In frameworks like Spring, particularly with its application event mechanism.
+
+## Consequences
+
+Benefits:
+
+* Loose Coupling: Components can interact without having direct dependencies on each other.
+* Flexibility: New subscribers or publishers can be added without impacting existing components.
+* Scalability: The pattern supports scaling components independently.
+* Reusability: The bus and components can be reused across different systems.
+
+Trade-offs:
+
+* Complexity: Introducing a data bus can add complexity to the system architecture.
+* Performance Overhead: The additional layer of communication may introduce latency.
+* Debugging Difficulty: Tracing data flow through the bus can be challenging, especially in systems with many events.
 
 ## Related Patterns
-Data Bus is similar to
 
-* Mediator pattern with Data Bus Members deciding for themselves if they want to accept any given message
+* [Mediator](https://java-design-patterns.com/patterns/mediator/): Facilitates communication between components, but unlike Data Bus, it centralizes control.
-* Observer pattern but supporting many-to-many communication
+* [Observer](https://java-design-patterns.com/patterns/observer/): Similar in nature to the publish-subscribe mechanism used in Data Bus for notifying changes to multiple objects.
-* Publish/Subscribe pattern with the Data Bus decoupling the publisher and the subscriber
+* Publish/Subscribe: The Data Bus pattern is often implemented using the publish-subscribe mechanism, where publishers post messages to the bus without knowledge of the subscribers.
+
+## Credits
+
+* [Enterprise Integration Patterns](https://amzn.to/3J6WoYS)
+* [Pattern-Oriented Software Architecture, Volume 4: A Pattern Language for Distributed Computing](https://amzn.to/3PTRGBM)