You can store your Boomi Flow runtime data externally; in a storage location of your choice.
Let’s use a hypothetical example to understand how powerful the new capabilities are. Say you want your runtime data to be in France, and the enterprise apps you build with Flow to be accessible only in Singapore. You can now configure this in a few minutes.
Here’s another. Say you want to store your runtime data in the UK, and never have it leave the UK; while restricting access to your apps to end-users based in the UK only. Sure.
Having an external data store outside the realms of where the Flow platform stores your runtime data, gives you even more granular control. With the new Flow capabilities, even though you are using a cloud-based app development platform, you can decide where your runtime data ultimately resides.
You can use the external data store to meet specific data residency and compliance requirements. You could, say, have your data reside only in a server inside your corporate headquarters in say, EMEA or APJ. Even though your app is available worldwide. Bespoke security configurations? Bring it on!
The Flow platform running multiple cloud instances in different regions gives you the power to run Flow apps wherever you want with even better content delivery.
Your data, where you want it. Your apps where you’d like them to be available.
[Note: This is a technology preview version and is not a production release. We recommend you wait till we finalize the features and launch the final production release to start using external storage for your production environment.]
You can set up an external data store anywhere you like. This could be on-prem, or with third-party providers like AWS or Heroku.
- We have detailed instructions on how to deploy an external store to Heroku, using our default implementation here.
- You can find Kubernetes example configurations, with health checking, and a test-ready database for the default implementation here.
- Find everything you want to know on how to use external storage with systemd for the default implementation here.
Of course, you can! Here is our External Storage API documentation.
Here is the implementation guide to setting up and running an external storage for your Flow runtime data. You are going to be using the Flow drawing tool to do this.
- Adding a data store
- Selecting a data store
- Enabling replication
- Migrating to a data store
- Disabling replication
Here is the implementation guide to setting up and running an external storage for your Flow runtime data. You are going to be using the Flow inbuilt API client to do this.
- Setting up storage in Flow
- Configuring your storage
- Migrating data to an external store
- Enabling data replication
Let’s make sure we are familiar with some key concepts:
Abbreviation for Application Programming Interface. An API is a software library or protocol that facilitates interaction between different software or services. You can find the Boomi Flow API documentation here.
Cloud computing is a way of using a network to access hardware/software based in a remote location, on demand. The Boomi Flow Drawing Tool is a cloud-based low code platform for app development.
The act of using and setting up data stores.
Location used to store your runtime data from the Boomi Flow platform externally. Also: The storage service that can store Flow states/data.
Heroku is a cloud application platform that lets developers build and run applications in the cloud.
Anything that is used specifically at runtime – states, service invoker logs, user tokens, etc.
Used by the external storage endpoint to decrypt incoming requests from the Flow platform, and to sign any outgoing responses that are sent back to the platform.
Used by the external storage endpoint to verify that incoming requests are indeed coming from the Boomi Flow platform (authenticity and non-repudiation). The platform key is also used to encrypt any responses that are sent back to the platform.