The following considerations should be taken into account while implementing this pattern:

• Performance: The message broker pattern adds another component to your system and therefore the involved services will experience additional latency in communication. Point-to-point communication has lower latency than communicating via a broker.
• Increased agility: This pattern helps isolate change to individual services. Due to loose coupling of services, this pattern facilitates changes in the application.
• High scalability: Due to loose coupling of services, each service can be individually scaled. This gives the application administrators fine-grained control of scaling the services.
• Ease of development: Since each functionality is isolated to its own service, developing a service or functionality will not affect the other services and functionalities.
• Load balancing: The services in a Microservice based application may get scaled at different rates. The messages broker queues requests waiting to be processed by the services which helps the services consume the messages at their own rates.
• Increased complexity: Communicating with message broker is more complex than point-to-point communication.