Downloaded 52 times
More Related Content
Similar to Mendix Cloud Hosting on CloudFoundry
Mendix Cloud Hosting on CloudFoundry
- 1.
- 2. The Mendix Cloud Theeasiest and cheapest way to operate Mendix Applications at Enterprise grade quality
- 3. Data Applications O/S Storage Servers Networking Containers Virtualization Runtime PaaS Mendix App Mendix Data ThePower of Cloud Traditional IT Storage Servers Networking O/S Containers (optional) Virtualization Data Applications Runtime YouManage=CICDScope IaaS Storage Servers Networking Virtualization O/S Containers (optional) Data Applications RuntimeYouManage =CICDScope Business Value, Agility & Cost Savings YouManage =CICDScope Scaling unit Vendor Managed Customer Managed CaaS (Container based PaaS) Storage Servers Networking Virtualization O/S Containers Data Applications Runtime YouManage =CICDScope
- 4. Ops Dashboard • Provisioning •Configuration • Staging • Backups • Monitoring & Alerting • Remote debugging • Log management CI / CD • Full API support • Jenkins / GitLab Key Features
- 5. Enterprise Grade Quality MendixCloud • Fully HA • Cloud Native • SLA: 99,95% • SOC 1 Type 2 certified • ISO 27001/2:2013 certified • ISAE3402 Type 2 certified • Pen tested against • OWASP • ISSAF • OSSTMM
- 6. Platform Architecture Components Models UserStories Apps, Users Apps & Modules Feedback Models Model Package Build Package Cloud Foundry Runtime Runtime Cloud Portal Build Server Package Repository Web Modeler Desktop Modeler Appstore Project Portal Team Server Status, Links Cloud Portal Project Portal Development Package References
- 7. Zone 1 Load BalancedRouting Layer Mendix Cloud Architecture Mendix ID Infrastructure as a Service Access & Security ServicesCloud Portal Controller Principles • Cloud Native • Follows 12 factor app methodology • Horizontally & Vertically scalable • Stateless architecture Technology • Cloud Foundry • AWS S3 • AWS RDS PostgreSQL Zone 2 EC2 Infrastructure API
- 8. Mendix Production CloudRegions Customer chooses Region • Different Apps can be hosted in different regions • An App is hosted in one region Backups are stored in a different AWS region Regions are added based on customer needs Mendix Cloud Region https://aws.amazon.com/about-aws/global-infrastructure/ AWS Region & Number of Availability Zones US East 1 (N. Virginia) EU West 2 (London) EU Central (Frankfurt) AP North East (Tokyo)
- 9. Environment ` App ContainerApp ContainerResources Strato, Meso (+), Iono (++), Magneto (+++) ` Runtime Container Mendix Cloud Node Mendix Cloud Cloud Node ProductionAcceptance (optional) Test Environment `App Container Environment ` App Container Cloud Node: • A cloud node is connected to one App • Each cloud node needs an App Container • A cloud node contains multiple staging environments • Test (Optional for Enterprise customers only) • Acceptance • Production • Each staging environment can have a fallback environment • Typically only production
- 10. Private Cloud FreeEdition Vertical Scaling Self-Service (inside existing contract) <48hrs in case of new contract - Horizontal Scaling Self-Service - Health Manager & Auto Recovery Included Available for all editions Included Available for all editions Backup Retention Up to Indefinite based on retention schedule, between 14 days up to 1 year or longer Up to 1 year based on retention schedule, between 14 days up to 1 year Backup Restoration Self-Service - Enabling (custom) TLS/SSL Self-Service - Fallback Environment Add-on Package Available for Enterprise Customers - SLA Up to 99.95% - File Storage Included through S3 Included through S3 Required skillset None None Mendix Cloud Features
- 11.
- 12. Environment ` App ContainerApp ContainerResources Strato, Meso (+), Iono (++), Magneto (+++) ` Runtime Container Mendix Cloud Node Mendix Cloud Cloud Node ProductionAcceptance (optional) Test Environment `App Container Environment ` App Container Cloud Node: • A cloud node is connected to one App • Each cloud node needs an App Container • A cloud node contains multiple staging environments • Test (Optional for Enterprise customers only) • Acceptance • Production • Each staging environment can have a fallback environment • Typically only production
- 13. Mendix Cloud Environment Oneruntime InstanceAn App Container contains: • Runtime Container Resources • Database Service (PostgresRDS) • File storage (S3) Environment Strato, Meso (+), Iono (++), Magneto (+++) ` Database Service (RDS) ` File Storage Bucket (S3) `Runtime Container
- 14. Mendix Cloud Environmentwith Scaling Scaling two+ runtime instancesScaling run time instances: • Zero downtime in case of runtime failure • HA Scaling is completely self-services • Scaling within App container restrictions • Runtime containers need identical sizes Environment Strato, Meso (+), Iono (++), Magneto (+++) ` Runtime Container ` Runtime Container Additional Instances ` Database Service (RDS) ` File Storage Bucket (S3)
- 15. HA & AutoRecovery Auto recovery – within one AZ: • Utilizes Cloud Foundry Health Manager for the runtime containers • Downtime for runtime failure: 1.5 minutes on average • The database RDS (managed by AWS) has native health manager within AZ • AWS automatically restarts RDS on failure • AWS guarantees an SLA up to 99,5% • Is provide in both Pro & Enterprise edition Environment Strato, Meso (+), Iono (++), Magneto (+++) ` Database Service (RDS) ` File Storage Bucket (S3) ` Runtime Container ` Runtime Container CF Health Manager
- 16. Mendix Cloud Region AvailabilityZones Availability zones: • Two Availability Zones per Mendix Cloud Region • Full Environment hosted in one Availability Zone • Backups replicated across Availability Zones • Realtime PostgresRDS data backup • S3 provides standard replication • Daily backups are copied to other region Environment Strato, Meso (+), Iono (++), Magneto (+++) Additional Instances ` Runtime Container ` Runtime Container * S3 has standard replication across AZ Availability Zone A Availability Zone B ` File Storage Bucket (S3) ` Cloud Backup Repository ` Database Service (RDS)
- 17. Mendix Cloud Region EnvironmentStrato, Meso (+), Iono (++), Magneto (+++) Mendix Cloud – Fallback Environment Fallback contains: • RDS Database with Multi-AZ deployment (Hot spare) • Double Database Costs • Fallback environment on our pricelist • Maximum downtime to restore containers, < 15 minutes • SLA of 99,95% • Available for Enterprise Edition only (Platinum SLA) ` Database Service (RDS) ` Database Service (RDS) ` File Storage Bucket (S3) Cold Fallback ` Runtime Container ` Runtime Container * S3 has standard replication across AZ Availability Zone A Availability Zone B ` (Fallback) Runtime Container
- 18. Mendix Cloud Region EnvironmentStrato, Meso (+), Iono (++), Magneto (+++) Mendix Cloud – Fallback Environment Auto recovery • Utilizes Cloud Foundry Health Manager for the runtime containers • Downtime for runtime failure: 1.5 minutes on average • The database RDS (managed by AWS) has a similar recovery mechanism within AZ • Default for all Cloud configurations Fallback Database: • RDS Database with Multi-AZ deployment (Hot spare) • Double Database Costs • Fallback environment on our pricelist • Maximum downtime to restore containers, < 15 minutes • SLA of 99,95% • Available for Enterprise Edition only ` Database Service (RDS) ` Database Service (RDS) ` File Storage Bucket (S3) Cold Fallback ` Runtime Container ` Runtime Container * S3 has standard replication across AZ Availability Zone A Availability Zone B ` (Fallback) Runtime Container CF Health Manager
- 19. Other Benefits • Fast& Seamless go-live • Expertise within Partner Eco System • Mendix support is much more efficient • Optimized for Mendix (performance) • Completely open (APIs ready for any CICD tool)
- 20.
Editor's Notes
- #6 Full HA capable. Mendix has adopted the ISO27001:2013 framework. All controls are audited against an ISAE3402 Type II assurance standard, which is the International equivalent of a SOC1 Type II report. Annual test performed by an external auditor based on the 3 listed frameworks. Vulnerabilities impacting customer app will be communicated within 36 hours of detection. On request more info about the pen-test can be verbally provided, detailed findings are company confidential. 3th party pen test is allowed, only on the customer application
- #7 All platform components are hosted in the Mendix Cloud in EU (Frankfurt), the Runtime containers are hosted in the region of choice.
- #9 The primary hosting locations are as follows: Mendix Cloud EU: AWS Frankfurt Germany Mendix Cloud EU: AWS London UK Mendix Cloud US: AWS North Virginia USA Mendix Cloud Asia Pacific: AWS Tokyo Data will always be stored in the same political region for the following regions: Data in the EU, including backups, will stay within the EU Data in the US, including backups, will stay within the US Based on customer needs additional regions could be made available.
- #10 Each Mendix App can have 1 Mendix Cloud Node. A Mendix cloud node has a Production and Acceptance Environment. Optionally a third Environment can be added ‘Test’. Each environment takes an ‘App Container’, based on the purchased ‘App Container’ and cloud options a different setup is made available.
- #13 Each Mendix App can have 1 Mendix Cloud Node. A Mendix cloud node has a Production and Acceptance Environment. Optionally a third Environment can be added ‘Test’. Each environment takes an ‘App Container’, based on the purchased ‘App Container’ and cloud options a different setup is made available.
- #14 A standard App Container provides a Runtime container, an Amazon RDS database container and an S3 file storage bucket The size and capacity of these containers depends on the Cloud Edition that has been purchased (Strato, Meso, Iono, Magneto)
- #15 With Mendix 7.0 and higher Horizontal scaling is available Self-service through sliders, scaling can be configured within the contract parameters Runtime containers must be identical in size. Zero downtime for application failure (traffic gets automatically redirected to different runtime containers)
- #16 A standard App Container provides a Runtime container, an Amazon RDS database container and an S3 file storage bucket The size and capacity of these containers depends on the Cloud Edition that has been purchased (Strato, Meso, Iono, Magneto) With Mendix 7.0 and higher Horizontal scaling is available Self-service through sliders, scaling can be configured within the contract parameters Runtime containers must be identical in size. Zero downtime for application failure (traffic gets automatically redirected to different runtime containers)
- #17 CloudFoundry provides a health manager, this HM automatically detects if a container fails. In case of a container failure a the runtime container is replicated and started Replication of a container and starting an average Mendix application normally takes 1.5 minutes. A 60 second timeout + restarting the application (Larger projects with long startup time will take longer to recover) Next to the Mendix/CloudFoundry health manager, we also leverage the RDS health manager function. AWS detects a downtime Per environment a total SLA of 99.5% measured per month
- #18 The Mendix / CF infrastructure choses 1 AZ to run the environment in (equally dividing all environments across both AZs). This is to keep latency between db and runtime low. To guarantee data availability backups are stored in a different AZ or different Region.
- #19 Fallback environment provides a second RDS instance in the second AZ. In case of failure all communication will be redirected to fallback RDS. When RDS comes back online that RDS will serve as the Fallback AWS specifies that failover takes typically 60-120 seconds. http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.MultiAZ.html Multi-AZ runtime container functionality will remain the same Per environment a total SLA of 99.95% measured per month (max 20.2 minutes of downtime per month) S3 inherit architecture already facilitates multi-AZ hosting
- #20 CloudFoundry provides a health manager, this HM automatically detects if a container fails. In case of a container failure a the runtime container is replicated and started Replication of a container and starting an average Mendix application normally takes 1.5 minutes. A 60 second timeout + restarting the application (Larger projects with long startup time will take longer to recover) Per environment a total SLA of 99.5% measured per month Fallback environment provides a second RDS instance in the second AZ. In case of failure all communication will be redirected to fallback RDS. When RDS comes back online that RDS will serve as the Fallback AWS specifies that failover takes typically 60-120 seconds. http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.MultiAZ.html Multi-AZ runtime container functionality will remain the same Per environment a total SLA of 99.95% measured per month (max 20.2 minutes of downtime per month) S3 inherit architecture already facilitates multi-AZ hosting