content_image/993870.jpg
GLYPH<SM590000> Gaining insight from historical data: By listening to and processing an event stream, you can gain insights based on time-based event patterns. Furthermore, because event streams also provide an event history, you can use this history to train machine learning models to progressively evolve the sophistication of the insights, as shown in Figure 3-27. 

<img src='content_image/993870.jpg'>

## 3.4 Capability perspective: Files and Business-to-Business 

Modern approaches to integration are often focused around synchronous exposure over web services and RESTful APIs. It is easy when focused on these patterns to forget that for many enterprises, especially in sectors such as retail, there is still significant reliance on traditional Business-to-Business (B2B) integration, such as Electronic Data Interchange (EDI). 

Can an API-led strategy be used for B2B integration? To what extent can you enable the same type of collaborations over APIs between business partners and the enterprise as are done by using EDI over a Value Added Network (VAN)? 

Let’s explore this situation from a few different perspectives: architecture, time, and cost. 

GLYPH<SM590000> Architecture 

B2B data exchanges through EDI have three core technological elements: transport protocol, data transformation, and partner management. They also are present in an API management capability, such as IBM API Connect, in a slightly different form. 

GLYPH<SM590000> Time: 

– Rapid onboarding. New partners must be onboarded quickly. Although partner management has been a core part of B2B and EDI for some time, API management technology has in recent years placed a focus on developer community enrolment to support rapid data access and exchange. 

– Development time. Most modern applications already come with an API by default to enable them to be more quickly incorporated into new solutions. Furthermore, most modern languages can call APIs natively. 

– Real-time information exchange. Traditionally, B2B and EDI patterns were focused around supporting messages for purchasing and supply chains. They are often batch-based in nature. With an increased business need for real-time data, for example, to manage critical path supply chain decisions, APIs better enable real-time data exchanges between applications and business partners. 

