Mendix Charting/dashboarding options:
- E-Charts (Community supported) are simple and nice,
- Anycharts (very common),
Grafana can be integrated, but I haven't tried it with Mendix.
Power BI can show reports using an iFrame widget. I like this approach.
Module/Widget Support Note: Check whether libraries are supported by Mendix/Platform or Partner.
Community-supported obviously can be changed by the community. Partner-supported is also an option if you have an agreement with the partner or trust them.
Performance Testing Tool options:
A colleague has used JMeter and feels it was not ideal.
I'm considering using the Microsoft Playwright Testing service and Playwright testing.
Enterprise Logging/SIEM SaaS integrations supported by Mendix:
- App Dynamics.
- Datadog,
- New Relic,
- Dynatrace, and
- Splunk
Watch out for:
Logging
Each system logs to loc files on the local machine; these can be pushed into the Postgres local instance. This can result in a massive storage load being added for auditing and logging.
Monitoring
Logs can be shipped out using backup and restored or by calling the REST Open API.
Maintenance
Mendix builds a database per app per environment, so the recommendation is to use at least 3 per app as you need dev, Test, and Prod. Each instance, by default, uses PostgreSQL (you can only use PostgreSQL if you use the Mendix-provided images deployed on AWS).
Global Variables
Mendix doesn't have a concept of a global variable at the start or per session. You can load lookup data, which is often held centrally in your enterprise. This can get heavy quickly, but you can copy Open API results into the local PostgreSQL database so it only gets local data.
Costs
With Mendix, the cost can escalate rather quickly. Reduce cost by scaling back to the most minor instance in dev and test, especially post-go-live. Each app has a separate database, so management and connectivity can become hard to control.
Performance
Number of Controls & Size of each application.