Using configurable bindings

IBM Financial Services Workbench provides several bindings to abstract the modelling part from the implementation part. This allows to use an identifier of such a binding while modelling a project and later, when implementing, the user has the option to edit the value of these bindings. This is especially helpful when working on multiple stages that require different settings of the deployments.

If you were working on three different stages (DEV, TEST, PROD), it is most likely that your deployments must meet different requirements on each of those stages. If they were configured inside the project itself, one had to edit code inside the project when moving to the next stage. By using bindings, this can be done very easily simply by editing the bindings value. This can be compared with using environment variables, where a program just searches for a given key and reads its value. While the value can differ on each environment, the key always remains the same.

IBM Financial Services Workbench offers two binding types that can be directly used inside projects. There are other binding types that are used for service configuration (e.g. message hub service bindings, IAM bindings, etc.) but on project level there are only the following two types relevant.