Unlike traditional IDEs such as IntelliJ IDEA, where version control tracks changes to source code files, Mendix uses a model-driven approach where applications are represented as structured models. Version control is still based on Git, but collaboration and conflict resolution require understanding changes to visual models rather than only comparing text files.
| Aspect | Mendix | IntelliJ IDEA |
|---|---|---|
| Version control model | Model-based versioning | File-based versioning |
| Primary artifact | Application model (domain models, microflows, pages, etc.) | Source code files (Java, Kotlin, XML, etc.) |
| Typical VCS | Git (through Mendix Studio Pro integration) | Git, SVN, Mercurial (via IDE integrations) |
| Merge experience | Model-aware merging with Mendix tools | Text-based diff and merge tools |
| Collaboration style | Multiple developers working on application models | Developers editing code files directly |
| Branching | Supported through Git workflows | Supported through Git workflows |
| Conflict resolution | More complex because changes can affect models | Usually line-based conflicts in files |
| Code review | Less natural for visual changes, better for generated/custom code | Natural through pull requests and code diffs |