Why It Matters: Properly using microflows and nanoflows can minimize the amount of data processed at any given time, improving overall performance. Microflows run on the server, while nanoflows run on the client side. Efficient use of these flows ensures that heavy processing tasks don’t bog down your server and that data is processed as close to the user as possible. This can significantly reduce latency and improve the user experience. Furthermore, small optimizations in working with lists in microflows can significantly improve the process time.

How to do this:

• Use nanoflows for client-side tasks to lighten the server’s load. Also here the Mendix best practice bot will let you know when there are microflows that can be converted to Nanoflows. Keep an eye out for that!
• Divide complex microflows into smaller, reusable pieces.
• Ensure microflows handle only the necessary data, avoiding unnecessary loops over large lists.
• Limit database retrieves in a loop. Try to retrieve the whole list of object you need outside the loop and use the “Find” functionality to search in that list. This prevents making a connection to the database for every iteration of the loop.
• Be smart about using the “continue event” or the “Break event”. Make sure you don’t continue the loop when you don’t have to.