@minka/bridge-sdk v2.11.0

Bridge SDK

Components

Bridge SDK provides two main components:

• Server
• Processor

Server

Server implements two-phase protocol for the ledger. Incoming requests are persisted in the bridge database as entries, intents and commands. When processing is requred, job is created which will be assigned to an available processor for processing.

Server provides proxy to the ledger in order for 3rd party system to be able to communicate with the ledger. Proxy will establish secure communication when calling the ledger and sign payload with the bridge key when needed.

Effects can also be registered in the server. Effects are used to extend the ledger core functionalities by observing and reacting on events raised when a change occurs with ledger data.

Exposed two-phase commit endpoints:

Exposed job endpoints:

Exposed proxy endpoints:

Exposed effects endpoints: | Method | Path | Description | | ------ | ------------------------------------- | ------------------------------- | | POST | /v2/effects/<handle> | executes a registered effect |

Processor

Processor listens for pending jobs in the system and executes them. Each processor must have unique handle in the system which is used for job balancing across processors. Processing of a job can be suspended for predefined time (e.g. 5 minutes, waiting for banking core) or indefinitely which requires manual job continuation.

Running unit tests

Run nx test bridge-sdk to execute the unit tests via Jest.

Running lint

Run nx lint bridge-sdk to execute the lint via ESLint.