|
| 1 | +# Overview |
| 2 | + |
| 3 | +Integration in WSO2 Integrator: BI is the foundational space for defining, organizing, and managing integration artifacts such as services, data mappings, and connections. |
| 4 | +Integrations can contain either a single integration or multiple integrations grouped together as a workspace. |
| 5 | + |
| 6 | +## For single integrations |
| 7 | + |
| 8 | +When building a simple, standalone integration, you can work directly without a workspace. This approach is perfect for: |
| 9 | + |
| 10 | +- Quick, one-off integrations |
| 11 | +- Independent services with no strong dependencies |
| 12 | +- Simple proof-of-concepts |
| 13 | + |
| 14 | +## For complex integrations |
| 15 | + |
| 16 | +Workspaces become essential when you need to: |
| 17 | + |
| 18 | +- Organize related integrations – Group multiple integrations that belong to the same business domain or application |
| 19 | +- Manage dependencies – Allow integrations to reference and use resources from other integrations within the workspace |
| 20 | +- Simplify collaboration – Work on multi-integration projects with a clear organizational structure |
| 21 | + |
| 22 | +### What is a workspace? |
| 23 | +A workspace is a collection of integration packages that can be organized and managed together in a single structure. This allows you to organize multiple related integrations in a single project structure. It provides a centralized environment where you can develop, manage, and maintain interdependent integrations. |
| 24 | + |
| 25 | +???+ Note |
| 26 | + This feature is available from WSO2 Integrator: BI 1.5.0 onwards and Ballerina version 2201.13.0+. |
| 27 | + |
| 28 | +### Key benefits |
| 29 | + |
| 30 | +- Visual Organization – See all your related integrations in one place with an intuitive tree structure |
| 31 | +- Seamless Navigation – Quickly switch between integrations without leaving your workspace |
| 32 | +- Dependency Management – Integrations within a workspace can reference each other automatically |
| 33 | +- Flexible Structure – Start with standalone integrations and convert them to workspaces as your project grows |
| 34 | +- Reduced Context Switching - Consolidate related repositories (e.g., code + documentation + config) into one view. This minimizes mental load and window management, allowing developers to focus on the logical feature rather than the repository structure. |
| 35 | +- Cross-Project Symbol Resolution - Enable "Go to Definition" and intelligent code navigation across distinct repositories. This removes the need to build or publish local packages to see changes in dependent projects, accelerating the feedback loop. |
| 36 | +- Resource Optimization - Reduce the memory and CPU overhead of running multiple IDE instances. A single instance managing multiple roots lowers hardware requirements and improves performance on developer workstations. |
| 37 | + |
| 38 | + |
| 39 | +Whether you're building a single integration or orchestrating a complex microservices architecture, WSO2 Integrator: BI provides the flexibility to work in the way that best suits your project's needs. |
| 40 | + |
| 41 | +Follow the below links to learn more about creating , managing workspaces and integrations: |
| 42 | + |
| 43 | +- [Creating an Integration](/developer-guides/workspace-management/create-an-integration) |
| 44 | +- [Managing Integrations in Workspaces](/developer-guides/workspace-management/manage-integrations-in-workspaces/) |
0 commit comments