Hello,
Yes, this is possible, but Mendix cannot be integrated using Module Federation like Angular components. Mendix runs as a full application, not just a frontend module.
The recommended and most practical approach is to embed the Mendix app inside your Angular app using an iframe. This allows the Angular app to act as the host and the Mendix app to behave like a micro frontend, without a full page redirect. Both applications can be deployed independently, which fits the micro frontend architecture.
For authentication, the best approach is to use SSO (OIDC, Azure AD, Auth0, etc.) so that when the user logs in to Angular, Mendix automatically recognizes the same user without asking to log in again.
In summary, Mendix can work as a micro frontend inside Angular using iframe embedding and SSO for authentication. This is the standard and recommended approach.
Thanks
ou cannot expose a Mendix module as a true Angular Module Federation micro-frontend.
Mendix apps are full SPA applications, not exportable UI components.
So:
Mendix runtime owns routing, state, session, and DOM root.
There are only 3 supported integration patterns:
This is the only fully supported UI embedding method.
Angular (host)
This maintains:
This is the architecture Mendix officially supports.
Example:
https://app.com/angular → Angular https://app.com/mendix → Mendix
Handled via:
User navigates without full domain redirect.
But still:
It is NOT true micro-frontend composition.
It is path-based application separation.
If your goal is true micro-frontend:
Use Mendix as backend only.
Expose:
Angular builds the UI fully.
This is the clean micro-frontend compatible architecture.
Mendix:
You cannot import it as:
loadRemoteModule()
Because it is not built as a federated module.
If using iframe or reverse proxy:
Use Single Sign-On:
Flow:
Angular → Identity Provider → Mendix
Both trust same IdP.
Session sharing via cookies is NOT recommended.
Use token-based SSO.
Best practice architecture:
Kubernetes ├── Angular (UI host) ├── Mendix runtime ├── Identity Provider (Keycloak / Azure AD) └── API Gateway
Authentication via OIDC.
UI integration via iframe or path routing.
True micro-frontend integration (Module Federation style) between Angular and Mendix is NOT supported.
Mendix is a full SPA runtime and cannot be exported as a federated UI module.
If you need micro-frontend architecture:
Those are the only production-safe approaches.