Development environment comparison

In BAMOE Canvas, creating a new file, trying a sample, or cloning a repository from the welcome screen will initialize a new workspace. A workspace is a lightweight environment where users can begin modeling assets immediately. If the workspace is not already a Maven project, users can apply a BAMOE Accelerator to expand it into a full project structure.

BAMOE Accelerators are project templates that include the necessary folder structure, configuration files, and dependencies. Users can choose between the Full BAMOE Accelerator, which supports both workflows and decisions, or the DMN BAMOE Accelerator, which is focused on decision services.

For developers using the BAMOE Developer Tools for VS Code, the recommended way to start a new project is to clone a BAMOE Accelerator from a Git repository. This provides a ready-to-use project structure with all required dependencies and configurations for building and testing Business Service projects.

Alternatively, developers can manually create the folder structure and configure the project using standard Maven conventions. While this approach offers more flexibility, it requires familiarity with the necessary dependencies and project layout.

In both cases, the project is managed as a standard Maven project, with all assets stored as plain text files. This makes it easy to integrate with Git for version control and to use Maven for building, testing, and packaging.

BAMOE Canvas offers a streamlined, browser-based environment for modeling and reviewing business assets. It supports both BPMN and DMN modeling through intuitive graphical editors. Users can start from scratch, import existing files, or explore sample projects directly from the BAMOE Canvas welcome screen.

The Problems tab offers real-time validation, and the DMN Runner enables users to test decision models directly in the browser using sample input data, making it easy to iterate and validate logic.

The BAMOE Developer Tools for VS Code offer a full-featured environment for developers to author and manage BPMN, DMN, and SCESIM assets. The extension leverages the built-in VS Code Problems tab to provide real-time validation. It also supports generating user task forms and integrates with Maven for validation, testing, and packaging. This setup gives developers full control over the development lifecycle using familiar IDE workflows.

BAMOE Canvas includes built-in Git capabilities directly in the browser. Users can initialize a Git repository from a workspace, clone existing repositories from platforms like GitHub, GitLab, or Bitbucket, and perform common Git operations such as commit, push, and pull—​all without leaving the BAMOE Canvas interface.

To enable communication with external Git providers, BAMOE Canvas uses the BAMOE CORS Proxy, which must be configured in the BAMOE Canvas settings. Users also need to provide Git credentials or personal access tokens to authenticate with their chosen Git provider. Once configured, business users can collaborate on shared repositories without needing to understand Git internals or use a command-line interface.

This approach allows business users to contribute directly to the same codebase as developers, using a visual interface that abstracts away the complexity of Git.

In contrast, the BAMOE Developer Tools for VS Code rely on the developer’s local Git installation. Git operations are performed using the built-in Git support in VS Code or through the command line, offering full control and flexibility for experienced users.

This setup is ideal for developers who are already familiar with Git workflows and want to integrate version control into their broader development process. It also allows for advanced Git features such as branching strategies, submodules, and integration with CI/CD pipelines.

While BAMOE Canvas simplifies Git for business users, the BAMOE Developer Tools for VS Code provide a more powerful and customizable Git experience for developers working in a traditional IDE environment.

In BAMOE Canvas, authentication is configured per Git. When connecting to a Git repository, users must authenticate using credentials or a personal access token associated with their Git provider (e.g., GitHub, GitLab, or Bitbucket). This is done through the Accounts modal in the Canvas settings, where users can manage their authentication sessions.

User management is handled externally by the Git, meaning that BAMOE Canvas does not maintain its own user directory. This simplifies administration and allows organizations to leverage existing identity and access management systems.

The BAMOE Developer Tools for VS Code rely on the developer’s local Git configuration for authentication. When interacting with remote repositories, authentication is handled by the Git client, which may prompt for credentials, use SSH keys, or access stored tokens depending on the user’s setup.

This approach gives developers full control over how they authenticate and manage access to repositories, and it integrates seamlessly with enterprise Git workflows and credential managers.

By shifting authentication to Git, BAMOE version 9.2.x eliminates the need for centralized user management within the platform itself, offering a more flexible and secure model that aligns with modern development environments.

While BAMOE Canvas itself does not perform builds, it supports development deployments through the Dev Deployments feature. This allows users to deploy their models to a Kubernetes or OpenShift cluster for testing purposes. The deployment process is configured through the BAMOE Canvas settings, where users can define the target cluster and credentials.

This feature is especially useful for business users who want to validate their models in a live environment without needing to understand the full build and deployment pipeline. It bridges the gap between modeling and runtime testing, enabling faster feedback loops.

For developers, the BAMOE Developer Tools for VS Code provide full control over the build and deployment process. Projects can be built using standard Maven commands, and the resulting artifacts can be deployed to any supported runtime, including Kubernetes, or OpenShift.

Developers can also configure local or remote development environments, use containerization tools like Docker, and integrate with CI/CD systems. This flexibility allows teams to adopt modern cloud practices and tailor their deployment workflows to their specific needs.