Skip to Content

Mendix is a rapid application development platform which can be used to quickly build apps without coding. This year at SAP TechED, I was excited to hear Björn Goerke announcing SAP’s partnership with Mendix. There is a lot of interest in the market around High-productivity application PaaS (hpaPaaS) and Mendix is one of the leaders in the hpaPaaS magic quadrant. This partnership addresses a gap in SAP Cloud Platform which will now enable customers to deploy applications in a much faster pace. If you are still thinking how this is relevant to you, check out this blog post “New Low Code Application Development Tool” by Michelle Huang

What I also like about this approach is that both SAP and Mendix share the same technology vision and leverage open standards like Cloud Foundry. So if a customer decides to use Mendix, they could rapidly build apps and deploy them to SAP or any other Cloud Foundry based PaaS.

I would like to highlight that you can only deploy Mendix applications to Cloud Foundry environment of SAP Cloud Platform and not the Neo environment.

Here is how the Mendix Desktop Modeler looks like.Yes, you need to install this small software on your laptop to develop your applications.

Mendix also has a WebUI modeler to do the same using a web browser. This is still in beta, but you can explore the capabilities by setting up a trial account.

I have compiled a video where I show how to use the Mendix toolsets to create a Fiori Application and deploy it to SAP Cloud Platform. Hope you find it interesting.


To report this post you need to login first.


You must be Logged on to comment or reply to a post.

    1. Murali Shanmugham Post author

      Thanks Nic. My understanding is that SEAM is a RAD Tool focused for developing iOS native mobile apps whereas Mendix is a RAD tool aimed at building cross platform web apps which can be deployed in Cloud Foundry environments.

  1. Mike Doyle

    Thanks Murali, the video was very informative. I’m skeptical of the power of ‘zero-code’ solutions, but as luck would have it this week I read this article:

    Whenever programming has taken a step away from the writing of literal ones and zeros, the loudest objections have come from programmers. Margaret Hamilton, a celebrated software engineer on the Apollo missions—in fact the coiner of the phrase “software engineering”—told me that during her first year at the Draper lab at MIT, in 1964, she remembers a meeting where one faction was fighting the other about transitioning away from “some very low machine language,” as close to ones and zeros as you could get, to “assembly language.” “The people at the lowest level were fighting to keep it. And the arguments were so similar: ‘Well how do we know assembly language is going to do it right?’”



Leave a Reply