Integrating Corda into the Wider Ecosystem

Corda is usually deployed as part of a wider ecosystem of applications in a modern enterprise. There are two possible integration points:

• Corda REST API
• External Messaging API

Each integration point has a specific purpose.

Corda REST API

The Corda REST API is the primary way in which external applications interact with CorDapps Corda Distributed Application. A Java (or any JVM targeting language) application built using the Corda build toolchain and CorDapp API to solve some problem that is best solved in a decentralized manner. . This API allows external systems to start flows Communication between participants in an application network is peer-to-peer using flows. , monitor the flow status, and retrieve the output of a flow. This REST API uses JSON for requests and responses, and flows can output data in any text representations. This provides flexibility to external systems around how they interact with Corda.

Because flows have access to a JVM compatible language along with a REST API, they can be built to create a rich, custom CorDapp not just to initiate flows that interact with peers, but also flows that return or search the data in the vault A database containing all data from the ledger relevant to a participant. The database tracks spent and unspent (consumed and unconsumed) states. of a virtual node The combination of the context of a user and the ephemeral compute instances created to progress a transaction on that identity's behalf. , for example.

External Messaging API

The external messaging API provides a second way to interact with external systems. This API allows a CorDapp, from within flow code, to publish a message on a predefined Kafka The means by which Corda workers communicate, acting as a central message bus between the worker processes. topic which can then be consumed by an external system. This provides an integration point from within a CorDapp, as opposed to the REST API which provides integration points around a CorDapp.

Corda 5.2 provides only outbound connectivity. That is, a flow can send a message, but not receive one. A future version may support both send and send-and-receive messages.