Schedule a Call

Solution Brief

Adopting a distributed API and Event-Driven Architecture

Faster decision making

The ability to capture and respond to events in real-time puts you in the driver's seat to make better decisions without delay

Business agility 

With real-time insight into the critical events happening in your business, you can leverage automation and AI to respond in real-time 

Reduce costs

The ability to respond in real-time means you can  take proactively optimise your supply chain and extend the life of your assets

Adopting Event-Driven Architecture

The key to doing business in real-time is establishing a modern digital backbone that enables better and faster decision making to deliver business agility and reduced cost. The modern digital backbone is underpinned by a cloud native architecture that can support a distributed API and event-based architecture.

This distributed architecture is heavily based on an interconnected network of APIs and Events. APIs are used for exposing business functionality securely in a consistent manner that is consumable by internal and external entities in a self-service capacity. They are mostly synchronous and stateless in nature.  Events, on the other hand, are inherently asynchronous and represent emission of key state changes within and outside the application. These changes can be subscribed to by various consumers, and if the change impacts them, they can take actions in accordance with their expected behaviour.

This is where events complement APIs perfectly, and together, they can be combined to solve almost every communication problem within or outside an application in a loosely coupled manner and thereby enable real-time business. Event-driven architecture (EDA) is a software architecture paradigm promoting the production, detection, consumption of, and reaction to events. EDA is common in microservices, cloud-native, IoT, event-driven Integration, streaming to AI/ML. The Publish-Subscribe (Pub-Sub) concept relies on events - “producers” describe the event they are publishing with event tags, known as topic taxonomy and “consumers” attract events using patterns and wildcards - this is true decoupling. Broadcasting events from the publisher (decoupling) allows additional uses of events later. This is key to agility.

Adopting event-driven technology cuts across the entire enterprise IT landscape of organisations. It’s important to remember that it’s not a replacement for existing thinking, but a way of getting value from the events that are happening in an organisation. We can think of becoming event-driven as a 3 step process.

  • Firstly, we have events already occurring in our systems. Publishing these events as they happen liberates the events from their respective data silo’s and allows innovation decoupled from the existing applications.

  • As we go through application modernisation and digitise more of the platform we can extend the digital backbone into the cloud and modern microservices-based applications. Events also act as a buffer to isolate legacy applications from bursty modern applications.

  • Finally, we can extend participation to partners, customers and other LoBs allowing real-time interaction and visibility.

Our cloud-native architecture blueprint provides a best of breed architecture leveraging market-leading platforms - Solace enabling the distributed event-mesh and MuleSoft Anypoint Platform managing the application network - complementing each other perfectly to enable the real-time business.

This Solution Brief provides a summary of the cloud-native architecture blueprint leveraging our best of breed platform partners - MuleSoft Anypoint Platform and Solace PubSub+ Platform.

 

Download Data Sheet