Flow Architecture - Software Integration

A New Approach to Software Integration. Flow is a concept in networked software integration that is event-driven, loosely coupled, highly adaptable and extensible. It is defined by standard interfaces and protocols that enable integration with minimal conflict and toil. Although there isn’t a universally agreed-upon standard for flow today, it’s poised to drive significant changes in integrating businesses and other institutions.

Key Properties of Flow

Flow is the movement of information between disparate software applications and services. It is characterised by the following:

• Consumers (or their agents) request streams from producers through self-service interfaces.
• Producers (or their agents) choose which requests to accept or reject.
• Once a connection is established, consumers do not need to request information actively—it is automatically pushed to them as it is available.
• Producers (or their agents) maintain control of the transmission of relevant information—i.e., what information to transmit, when, and to whom.
• Information is transmitted and received over standard network protocols—including to-be-determined protocols precisely aligned with flow mechanics.

Flow and Integration

Flow and event-driven architectures are exciting as they are crucial in our economic system’s evolution. We are quickly digitising and automating the exchanges of value—information, money, and so on—that constitute our economy. However, most integrations we execute across organisational boundaries today are not in real-time, and they require mostly proprietary formats and protocols to complete.

The World Wide Flow (WWF)

The global activity graph is the World Wide Flow (WWF). The WWF promises to democratise the distribution of activity data and create a platform on which new products or services can be discovered through trial and error at low cost. The WWF promises to enable automation at scales ranging from individuals to global corporations or even global geopolitical systems.

Flow and Event-Driven Architecture

Event-driven architecture (EDA) is the set of software architecture patterns in which systems utilise events to complete tasks. EDA is a loosely coupled method of acquiring data where and when it is valid, like APIs. However, its passive nature eliminates many time- and resource-consuming aspects of receiving “real-time” data via APIs. EDA provides a more composable and evolutionary approach to building event and data streams.

The Ancestors of Flow

There are plenty of examples of real-time data passed between organisations today, but most don’t flow, as defined here. Generally, existing streaming interfaces are built around proprietary interfaces. The producer typically designs the APIs and other interfaces for their purposes only or is being utilised for a specific use case, such as industrial systems.

Code and Flow

If we are looking at the flow basis, we must look at another critical trendsetting the stage. “Serverless” programming depends on the system’s flow of events and data. The increased adoption of managed queuing technologies such as Amazon Managed Streaming for Apache Kafka (Amazon MSK) or Google Cloud Pub/Sub, combined with the rapid growth of functions as a service (FaaS) code packaging and execution, is a valid signal that flow is already in its infancy.

In conclusion, flow is a promising concept that could revolutionise integrating software and systems. Flow could unlock a new level of automation and efficiency in our digital economy by enabling real-time, event-driven communication between disparate systems.