I built DMM Infinity for Mendix to close the selective-data-transfer gap. Now on the Marketplace and asking: where does it hold up, and where does it break? - Mendix Forum

I built DMM Infinity for Mendix to close the selective-data-transfer gap. Now on the Marketplace and asking: where does it hold up, and where does it break?

0

Hi everyone. I'm Raul Coelho, Certified Mendix Software Architect at Infosistema. I built DMM Infinity for Mendix, which just went live on the Marketplace. I'm posting here because this community knows Mendix internals better than any outside team ever will, and I'd genuinely like your feedback, including the unflattering kind.


A bit of honest disclosure up front: I'm directly involved in the product, so treat this as a vendor post.


Why I built this


On one of our first Mendix projects at Infosistema, we hit a wall that is probably familiar to most people here. The user had done all the setup configuration in the Acceptance environment. We needed to push that configuration data into the Production environment. The platform gave us clean ways to refresh a full environment, but nothing for selectively moving a specific slice of data between environments.


So we built custom microflows. They worked, until the next project, where we built them again, slightly differently, because the app was different.


Over the next few projects the use-case list grew:



Every team I have compared notes with seems to have lived some version of this. It kept bothering me that the answer in the Mendix ecosystem was always "build another microflow".


What DMM Infinity does


Everything is managed in DMM Infinity. No custom microflows to build, no REST or OData endpoints to publish, no export operations to maintain as the domain model evolves, and no database credentials handed out to external tools:



Requires Studio Pro 9.24 or higher. There is a free plan for individual developers (no card, no trial expiry), which is the version I'd most like you to kick the tires on.


Marketplace: https://marketplace.mendix.com/link/component/258035
Product site: dmminfinity.com


What I would actually like from this thread


Three things, in order of usefulness to me:


  1. Use cases I have not considered. What selective-data or anonymization scenarios do you deal with on Mendix that I should make sure DMM Infinity handles?
  2. Where it breaks on real apps. Custom modules, unwanted side-effects you noticed during pipeline execution, Studio Pro 9 to 10 transitions where the domain model changes underneath you, unusual association patterns. If something feels fragile when you try it, please say so.
  3. Was the experience simple and flawless, or did you find friction? Friction in the setup, in the configuration UI, in reading the logs, anywhere. The small-papercut feedback is the kind I almost never get from internal testing.


Reply here if it's useful for others to see, or email us at support@dmminfinity.com if you would rather discuss privately. If any of you want to try it on a real Mendix app and give me the fully unfiltered version, drop us an email and I'll set up a private-pilot session with you, no marketing involved.


Thanks in advance. Not here for upvotes, here for the feedback.


Raul Coelho

Posted
0 comments