Question

Microflow VS Nanoflow along with use cases

0

Hello, I am a newbie in this field. I wonder if there are any use cases for microflows and nanoflows. I want to know specific examples. For instance, microflows are used for interacting with databases. I also read some documentation and found that nanoflows are executed when a user clicks a button. However, I couldn't imagine the specific context. In summary, I want to know when to use microflows and when to use nanoflows, along with use cases. It would be appreciated if you could provide some answers. Best regards,

asked 2024-06-18

Gain Lee

3 answers

2

Hi Gain Lee,

We should use microflows only if we have to apply some logic, that requires a huge DB connection or some server-side implementation.

If the process can be handled on the client side, we should use nanoflow only.

To know more you can visit this documentation: Microflow vs Nanoflow.

Hope it helps!

Rishabh

(Resilient It Services)

answered 2024-06-18

Rishabh Shandilya

0

Hi Rishabh Shandilya,

Your explanation is very clear and helpful — thank you for that.

But I still have one question:

Can we commit data into the database using a Nanoflow?

If your answer is no, then please try it once in Mendix Studio Pro.

Just create an object, perform a commit action inside a Nanoflow, and you will see that the commit actually works.

This is because:

Native mobile apps run nanoflows on the device, but
When a nanoflow contains server-side actions (like Commit, Call microflow, Upload file, Retrieve from database, etc.), Mendix automatically sends the request to the server.

So yes — nanoflows can commit data, as long as the app type and permissions allow server communication.

Thanks!

answered 2025-12-06

Hosyar Singh Lodhi

Sagi V K A V D Prasad Varma · Accepted Answer · 2024-06-18

HI Gain Lee,

This could help you understand the difference.

Microflows:
- Server-side execution: Microflows run on the server.
- Java compilation: They compile down to Java, allowing integration with third-party Java libraries and Java actions.
- Background tasks: Microflows are suitable for carrying out background tasks.
- Complex logic: Use microflows for more complicated tasks, such as retrieving and manipulating data.
- Rollback behavior: Errors during microflow execution roll back all changes within the transaction 1.
Nanoflows:
- Client-side execution: Nanoflows run directly in the client (browser or device).
- JavaScript compilation: They compile to JavaScript.
- Simpler tasks: Nanoflows are great for simpler tasks, like viewing data in a list view or performing quick validations.
- Offline apps: Currently, nanoflows are most beneficial in offline apps.
- No rollback: Errors in nanoflows won’t roll back previous changes 2 3.

Example Use Cases:

Microflow: Suppose you need to perform a complex data transformation or integrate with an external system using Java actions. In this case, a microflow would be appropriate.
Nanoflow: If you want to execute a quick validation or manipulate data directly in the client (e.g., updating UI elements), nanoflows are a better fit.