What is our primary use case?
We have very broad use cases for Mendix. We use it for internal applications and writing customer applications. We create advanced omnichannel telephony and CRM apps and even have Mendix apps that will be considered big-data apps, like our IoT solution in Agriculture.
We use Mendix to solve classical business problems, Risk solutions in fintech, Call Center apps, data processing, and used it to solve product development challenges that work well with rapid application processing for new product development. We do both new product development and also full largescale production systems on Mendix. We have solutions deployed on the cloud and on-premises.
How has it helped my organization?
We respond much quicker to challenges, our clients are more profitable and our staff love the opportunity to model and not write boring repetitive code.
What is most valuable?
One of the most valuable features in Mendix is its declarative model-driven development capabilities. Declarative development is important for the future of business software development; it allows us to rapidly model solutions without having to tell the computer how to do the basics. It allows us to focus on rich business logic rather than spending time managing boring technical details as is required with classical imperative development.
Mendix helps reduce the total cost of ownership: It validates workflows and system flows and this saves significant time when developing and maintaining apps. Refactoring is much easier in Mendix and done with more confidence.
Mendix apps are relatively quick to develop because it is a low-code platform. It's very robust, flexible, open, and scalable. It's for a low-code savvy customer. The tooling is also really good and it has good mobile app development capabilities with a platform suited to integration and publishing app services.
So in a nutshell, valuable features: Mendix declarative modelling, finely-grained security model, easy data modelling, easy app integration, tooling, validation, mobile development features, ease of debugging, extensibility and attention to detail of the Mendix core team.
What needs improvement?
We would like to see is the ability to version manage modules and not just the app. We need finer-grained version management for software repositories. Version management is good but it needs more work.
Also, because of the licensing model, Mendix apps are too monolithic. It would be great to have a microservices licensing model that works well for microservices especially designed to work with Kafka, Google Pub/Sub and streaming technologies.
We need much better code refactoring tools, like IntelliJ but for Mendix. For example, if I wanted to maintain all projects and refactor Domain model fields in bulk, it would be good to have intelligent renaming across the whole model with regular expression syntax. The modeller is too clickety-click.
The most important feature I'd like to see is support for is first-rate JSON Schema support and first-rate GraphQL support. Of course, the Modeller must run on Mac, not Windows.
Lastly, the licensing model does not scale well with many users. This is a huge problem as apps that have many users become very expensive and can kill the business case. Mendix is reasonably negotiable but it's a pain to deal with the licensing for each new project.
For how long have I used the solution?
I have been working with Mendix for 10+ years.
What do I think about the stability of the solution?
The stability is very good. This is low hassle, low maintenance technology. We write systems for clients on Mendix and the few support issues we've gotten have been quick to fix. The performance is excellent.
What do I think about the scalability of the solution?
This product is scalable and it's relatively easy to scale. Because of its architecture, it can't scale like microservices that are designed for scaling across the globe, but Mendix has some horizontal and vertical scaling built in. It's not on the same level that you would get with a native cloud first node app. It's a little bit more limited, but there are still scaling options.
How are customer service and support?
I would say they're good, but I've never encountered a software vendor with excellent support.
Which solution did I use previously and why did I switch?
We tried others and settled on Mendix.
How was the initial setup?
The initial setup was simple. It's not difficult to do yourself.
What about the implementation team?
We implemented through an in-house team. There are six people in my company working with Mendix.
What was our ROI?
High, we do more with highly skilled engineers and love the speed of app development, especially the lower cost of maintaining apps over longer periods.
What's my experience with pricing, setup cost, and licensing?
Mendix seems expensive. But with Mendix, one needs fewer developers to achieve high velocity, and if your environment can achieve that, then the total cost of ownership is fine. It's not cheap, though and not all projects will benefit unless one has a bulk licensing agreement.
This product is licensed per application, per user. Mendix has other features you can access with a separate license, like Data Hub, but the base license has more than most people need.
Mendix needs much better React component/widget writing compatibility. it is still more difficult than it should be to add your own components.
Lastly, Low Code Tools are weak at developing multi-tenant apps. One quickly loses the speed advantage and running many apps gets too expensive and a maintenance hassle as these apps tend to be monolithic, partly due to licensing.
Which other solutions did I evaluate?
Yes, Outsystems but we much preferred Mendix's non-code generating style. Model Driven Development needs to run a model. We also did not like the licensing model of Outsystems.
What other advice do I have?
I rate this product a nine out of ten. If you consider adopting Mendix, rather build a new culture and a new team. Do not just try and use legacy software developers who are passionate about older technologies. Use Mendix adoption as an opportunity to integrate business and IT; build new teams that are supported by first-rate software engineers AND new business engineers who can focus on understanding both business and IT. This allows one to model the business, understand the business, and develop the right software.
Mendix is excellent for innovation. Whenever one has an opportunity for new product development, it's an excellent choice.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner