Mendix Expert Developer study guide
Mendix Expert Developer · Work through your exam, one topic at a time.
The Mendix Expert Developer credential is an advanced certification aimed at developers who already build Mendix applications fluently and want to demonstrate depth across the whole platform lifecycle, not just page building. It suits lead developers, solution architects, and senior engineers who own domain models, design integration layers, harden security, tune performance, and run CI/CD pipelines. The Mendix Expert Developer study guide has 9 sections and about 3,107 words.
01Domain Modeling and Data Architecture
This domain tests whether you can shape entities, attributes and associations that stay correct under real data volumes, security rules and change. Expect judgement questions: which relationship type, when inheritance pays off, and which modelling shortcut turns into a defect six months later.
386 words, about 2 min02Microflows and Application Logic
This domain checks that you can express business logic in the right artifact and that the logic survives large lists, failures and concurrency. Nanoflows execute client-side: no commits, no Java, no direct database retrieve.
342 words, about 2 min03Security and Access Control
This domain tests defence in depth: whether access is enforced at the model level rather than painted onto pages. Security levels are Off, Prototype/Demo and Production.
344 words, about 2 min04Integration and REST/SOAP/Web Services
This domain tests whether you can build integrations that fail predictably: correct mapping, correct authentication, correct handling of every status code you can receive. Consume REST offers a plain Send Request activity returning a string, or a mapping-based call that produces entities.
350 words, about 2 min05Performance, Scalability and Tuning
This domain tests whether you can find the bottleneck with evidence and fix it at the right layer - model, query or infrastructure. The database is usually the bottleneck.
340 words, about 2 min06Deployment, Environments and Cloud Operations
This domain tests the operational side: what a deployment package actually contains, how environments differ, and how to run production without surprises. A deployment package holds the compiled model, not the data.
326 words, about 2 min07Architecture, Modularity and Reusability
This domain tests whether you can draw boundaries that hold: modules that own their data, expose a contract and can be understood without reading everything else. Split by business capability (Catalog, Orders, Payments), not by technical layer (Entities, Microflows, Pages).
323 words, about 2 min08Testing, Quality Assurance and Troubleshooting
This domain tests whether you can prove the app works and diagnose it when it does not: model consistency, debugging, logging and layered automated testing. Consistency errors block deployment; runtime errors appear only under real data.
340 words, about 2 min09Version Control, DevOps and CI/CD
This domain tests whether you can run a Mendix team and a Mendix pipeline: branching that fits binary model files, and automation that builds once and deploys the same artifact everywhere. Team Server is Git-based.
356 words, about 2 min