Скачать или смотреть Catalyst Specialist Certification Maintenance (Winter '25)

#salesforce
#trailhead
#trailheadsalesforce
#salesforcetrailhead

Catalyst Specialist Certification Maintenance (Winter '25) :    • Catalyst Specialist Certification Maintena...  

Implement event-driven architecture (EDA) as part of your API-led strategy using the AsyncAPI support in Anypoint Platform. The MuleSoft Anypoint platform makes it easy to design, implement, deploy, and govern APIs. Recently, MuleSoft introduced advanced support for event-driven API architecture, support for implementation of AsyncAPI 2.6, which makes working with event-driven APIs as easy as working with REST APIs.

Catalyst users are familiar with REST APIs and the synchronous communication model: make a request and wait for the response. Typical web users understand this process; entering a URL in a browser address bar will send a request to a server, which then sends back website content as a response.

Event-driven architecture serves use cases where there’s no need for a response from the server. If you simply want to communicate that something happened, such as “a new user signed up,” then integrations can be based on events. Event-driven architecture is referred to as asynchronous communication since the integration doesn’t need to wait for a response. Imagine an intermediary holding information until another system needs it. The intermediary, or broker, simplifies the asynchronous handling of many interactions.

Now, suppose you want to send extra information along with the event, such as, “Here is the new user’s name and email address.” Once again, the system sending it doesn’t need a response—other than a confirmation that the broker received the message. Broadly speaking, there are two types of events: simple notification events and data events, which contain more information and context.

Notification events indicate that something has happened: a state change, such as “the order has shipped.” Notification events may be referred to as messages, identifiers, or notifications.
Data events carry additional information related to the state change, such as the product to ship, its price, and a shipping address. This data can then be used by other systems to perform further processing or actions.
Event-driven architecture expands your options to provide solutions. For some use cases, REST APIs and synchronous communications are less efficient and have a higher chance of failure due to excessive coupling (tight interdependencies between systems) and continuous polling (repeatedly checking for updates). Event-driven architectures help organizations build real-time business integrations with low latency and high resilience.

Let’s look at the common event-driven architecture patterns specialists use for these two types of events.