Workflow

IBM Industry Solutions Workbench covers the whole lifecycle of applications based on modern microservice architecture principles from design to day2 operations.

Manage your ecosystem

IBM Industry Solutions Workbench organizes your distributed development tools and assets in one aggregated view. Enable your development teams to transparently manage multiple services, versions and configurations.

Leverage domain-driven design

IBM Industry Solutions Workbench enables fusion teams to collaboratively capture business requirements in domain-driven design terms and automatically transform those into modern microservices.

Automate code-generation

The integrated Design2Code approach removes the limitations of traditional low-code approaches and enables your development teams to combine the speed and productivity of low-code with the flexibility of pro-code development within the same operational model.

Treat documentation as code

IBM Industry Solutions Workbench supports a broad set of in-line visualizations and all managed stacks support auto-generated diagrams, significantly reducing manual efforts to write comprehensive docs.

Automate path to production

Empower agile teams to build, test and deploy their own solutions: Based on managed stacks, developers turn source code into containers in minutes —automatically with every code commit.

Compose enterprise solutions

Application composition enables your team to build business solutions through composition of existing, to-be developed and externally sourced components. Components can be easily grouped for application-centric delivery across multiple stages.

Developing solutions with IBM Industry Solutions Workbench follows a certain workflow. It all starts and ends with applications in form of Application Composition Projects. This project type is used to compose applications by adding ready-to-use components and applying configuration.

Every application consists of multiple reusable components that are managed in a component repository. You can build your own components or (re-)use from a variety of built-in or 3rd party components. If you decide to build your own components, you can choose between Domain Services and Generice Services depending on your resources and project demands. Next, you choose a stack and an implementation language and there you go.

But application composition is more than just building components and putting them together. You also have access to two additional sources, the framework components (built-in) and external components (3rd party). This provides you with additional business capabilities that you can add to your next application to innovate even faster and with less risk.

10 steps to build an application:

1. Start with creating an Application Composition project
2. Add existing component(s) from the Component Repository
3. Configure these components to your needs
4. Create Planned Component(s) in case there is no suitable component
5. Create Service project(s) for each of the planned components
6. Design and implement these Service Project(s)
7. Release them to make them available as components
8. Replace planned components with the new components
9. Define one or more deployment targets for your application
10. Configure and deploy your application to one or more deployment targets

Read more about working with projects