Merging Multiple Mendix Application into One

0
Hi Team,We have multiple Mendix applications of one client developed on different Mendix versions.Client is asking if we can merge those applciation into one so they will have just one URL for all.Can you guide me is this possible and how? what will be pros and cons for this.Thank you.
asked
3 answers
0

Hi Snehal,


Yes, it's possible, but "how" depends on what you mean by "merge," and the approach has significant trade-offs.

Three approaches to consider


Approach 1 — True merge (consolidate into one Mendix app) Migrate all modules, domain models, pages, and logic into a single Mendix app on one version. This is the most thorough solution.

Approach 2 — Navigation hub with deep links Create a lightweight "shell" or portal app that acts as a single URL entry point, and deep-link users into each underlying app. Users see one URL, but the apps remain separate.

Approach 3 — Reverse proxy / URL routing (infrastructure layer) Put a reverse proxy (e.g. Nginx, API Gateway) in front of all apps, routing paths like /app1, /app2 to different Mendix runtime instances. One domain, multiple backends.


Each has it's pro's and cons. Let me know for future discussion I can help


answered
0

Create a new lightweight Mendix app as a "portal." It shows tiles based on user roles, and each tile links to the respective app's URL.

Each app keeps its own URL, security, and modules. The portal is just the front door.

How it works:

  • User logs in once via SSO
  • Sees tiles based on their role
  • Clicks a tile → goes to that app
User → Portal App → Tile → App A / B / C / D

Your 4 apps don't change at all. You're just building a front door that points to them.

answered
0

Hi Snehal,


Great discussion! To address your final concern about app performance

when merging — yes, it can get heavy, but it's manageable if done right.


On your specific concern about Java actions and Excel processing:


Having heavy Java actions (complex calculations, 1000+ records, Word/PDF

generation) inside a merged app is absolutely fine as long as you:


1. Run heavy processes asynchronously

- Use Mendix Scheduled Events or queued microflows so heavy Excel

processing doesn't block the main thread

- This prevents one user's heavy calculation from slowing down others


2. Separate your Java actions into dedicated modules

- Keep the Excel/calculation logic in its own module within the merged app

- This keeps things maintainable and isolated


3. Scale your cloud resources accordingly

- A merged app with heavy logic will need more memory/CPU

- On Mendix Cloud, increase your container size

- Consider a separate environment node for background processing


My honest recommendation for your scenario:


Given that you have:

- 4 apps on different Mendix versions (10.12 and 11.4)

- Heavy Java actions and Excel processing

- Different security models and modules


I would NOT do a true merge into one app. Instead, go with

the Portal/Hub approach:


- Build one lightweight portal app on Mendix 11.x

- Use SSO (SAML or OpenID) for single login

- Show role-based tiles on the homepage

- Each tile deep-links to the respective app

- Put all 4 apps + portal behind a single domain using

a reverse proxy (Nginx or Mendix API Gateway)


Result: Client sees one URL, one login, one homepage —

but each app runs independently with its own resources.


This is also best practice for enterprise Mendix setups

and avoids a risky, time-consuming merge of apps on

different versions.


Hope this helps!

Piyush

answered