Choosing the Right

Mendix Deployment
Model for Your Business
Clyde Waal / Cloud Architect / Mendix

MENDIX
WORLD
Mendix Apps Can be Deployed “Anywhere”

MENDIX
WORLD
 aPaaS Deployment Options

aPaaS
(Public Cloud)

MENDIX
WORLD
 Virtual Private Cloud Deployment Options

Virtual Private
Cloud

MENDIX
WORLD
Traditional On-Premise Deployment Options

Linux
Server

Traditional
On-Premise
Servers Windows
Server

MENDIX
WORLD
Services needed to run Mendix

MENDIX
WORLD
Services needed to run Mendix

MENDIX
WORLD
Services needed to run Mendix

MENDIX
WORLD
 Moving Away from Mendix Cloud
Increases Operational Burden…
On-Premise

• Traditional Linux/
Virtual Private Cloud
Operational Burden

Windows Servers
• Kubernetes
• Managed • Cloud Foundry
aPaaS Kubernetes
(AKS/EKS/GKE/
OpenShift Dedicated)
• Mendix Cloud • Cloud Foundry
• SAP Cloud
• IBM Cloud

Time-to-Value MENDIX
WORLD
…but Provides Capabilities that
May be Crucial to Larger Enterprises

Legacy Leverage Existing

(non HTTP-Based) Compliancy
Service Integration Arrangements

MENDIX
WORLD
 Legacy (non HTTP-based)
Service Integration
aPaas
(Mendix Cloud,
SAP, IBM Cloud) VPC On-Premise
Public
HTTP-based
Public
Non-HTTP based

• SAP Cloud
Private Connector
HTTP-based • Reverse Proxy
• API Gateway

Private
Non-HTTP based

MENDIX
WORLD
Leverage Existing Compliancy
Arrangements

Skip internal Leverage existing

approval procedures technical measures
for Cloud usage for secure Cloud usage

…and shorten time-to-value!

MENDIX
WORLD
 • VPC: Linux/ Windows/Docker
• On-Premise: Linux/ Windows/Docker
Integrate w/ legacy
(non-HTTP based)
YES
services?
YES

Less Than • VPC: Cloud Foundry

NO 3 apps? • On-Premise:
Cloud Foundry

YES
• aPaaS: Mendix NO
Cloud
• aPaaS: SAP Cloud • VPC: Managed
• aPaaS: IBM Cloud > 10 Apps Kubernetes
and CF NO • On-Premise:
Available? Kubernetes

This decision tree excludes MENDIX

Compliancy considerations WORLD
 Mendix Enterprise Deployment Trends
SAP & Virtual Private Traditional
Mendix Cloud
IBM Cloud Cloud On-Premise
• Fast majority of Mendix • Significant portion of • Majority of VPC • Majority of on-premise
(enterprise) customers Mendix customers on customers run on Azure customers run
deploy in Mendix the SAP cloud are Kubernetes Service. DIY traditional servers,
Cloud. existing SAP customers. Kubernetes (on AWS) followed by Cloud
• Legacy integration • Often have the desire to and AWS EKS are Foundry.
typically using HTTP use SAP Cloud runner-ups. Often • Recently rise in early
reverse proxies and API Connector to access managed by third-party adopters of Docker
gateways. SAP services. service provider. Swarm & Kubernetes
• CI/CD integration using • Azure DevOps most (namely Red Hat
Mendix Build & Deploy adopted CI/CD solution. OpenShift) on-
APIs, typically using Followed by Jenkins and premise. Often
Jenkins. Gitlab CI. managed by third-
• Collaboration between party service provider.
teams responsible for
Mendix and Operations
crucial for success. MENDIX
WORLD
Key Take-Aways
Mendix Expert Services is available
to assist you on this topic with:
• Tailored advice on choosing
deployment options in your
specific situation.
‣ aPaaS deployment models (Mendix Cloud,
• Organizational support in
SAP Cloud, IBM Cloud) provide great out-of- helping your Ops & Mendix
the-box value sufficient for the vast majority teams understand each other.
of apps. • Technical support in setting up
Mendix using the various
‣ Moving away from aPaaS comes with deployment options and
operational burden. Specific capabilities may achieving secure integration
make a move to VPC or on-premise desirable with legacy on-premises
services.
for (larger) enterprises.
‣ Upcoming Mendix Native Kubernetes
integration will soften the operational burden
and time-to-value disadvantages of VPC and
on-premise deployment options.

MENDIX
WORLD