Technical Solutions

Three options how to implement State-Management with Boomi

File-System

The simplest way to implement state-management with Boomi is using the file-system (Disk v2 connector). The (limited) state-management functionality should be implemented as re-usable Boomi sub Processes (process routes).

This solution is recommended for less than 100 states.

Boomi File-System Implementation

PRO

• Can be implemented with Boomi as-is.

  • No additional applications or services are required.

CON

• Limited capabilities to query and access states.

• Slow. Querying records with a certain state requires to read all files data.

• Managing states manually (working with files) is limited.

Database

Use any database, create a new table and manage states there.

The challenge with that is, that a database is s state-store only, not providing any state-management functionality. It requires a layer on top of the database, for example stored procedures or additional Boomi processes (like for file-system) to implement the state-management functionality.

PRO

• Fast

CON

• State-Management services have to be built on-top of the database, like API access for the customer.

• Requires a database, and a DB admin.

Web-Service

This is probably the easiest and most complete solution to use a web-service to manage states. You can build your own service - welcome to think about its requirements - or you can use it out of the box:

Intermediate Storage