ARTICLE

Applying AI to Existing Platforms

From AI as a Service by Peter Elger and Eóin Shanaghy

Integration Patterns for Serverless AI

ETL, Point to point and ESB

Figure 1. Typical enterprise technology estate, broken down by logical domain. This image is intended to illustrate the complex nature of a typical technology estate. The detail of the architecture is not important.
Figure 2. Simplified Enterprise Representation
  • Pattern 1: Synchronous API
  • Pattern 2: Asynchronous API
  • Pattern 3: VPN Stream in
  • Pattern 4: VPN Fully connected streaming

Pattern 1 Synchronous API

Figure 3. Integration Pattern 1 Synchronous API

Pattern 2 Asynchronous API

Figure 4. Integration Pattern 2 Asynchronous API
  • By constructing a web application that users can interact with to see results.
  • By the system messaging the results through email or other channels.
  • By the system calling an external API to forward on details of any analysis
  • By the bridge code polling the API for results

Pattern 3 VPN Stream In

Figure 5. Integration Pattern 3 Stream In

VPN

Pattern 4 VPN Fully Connected Streaming

Figure 6. Integration Pattern 4 Full Streaming

Kafka

Which Pattern?

Table 1. Applicability of AI as a Service legacy integration patterns

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Manning Publications

Follow Manning Publications on Medium for free content and exclusive discounts.