0

  I am currently designing the deployment strategy for multiple Mendix backend applications on an OpenShift virtual cloud (on premise, not cloud). These applications serve as the backend layer for multiple client applications (e.g., sales process, complaint process). Each backend app has a distinct role: 1. Master Data Management App - Stores shared business-critical information. 2. API Gateway App - Manages API integrations for all apps. 3. Deployment & Version Control App -Oversees updates and deployments across all applications. 4. Process-Specific Backend Apps -Handle business workflows and logic.   Given their high workload, performance, and stability requirements, I’m evaluating two deployment strategies: 1. Single Namespace for All Apps: - Easier shared resource management and networking. - Risk of resource contention and performance bottlenecks. - Security concerns if one app is compromised. 2. Separate Namespace per App: - Strong isolation for security and scalability. - Independent resource allocation for better performance. - More complex CI/CD and infrastructure management.   For those with Mendix on OpenShift experience, what would you recommend for a high-performance backend architecture? Have you encountered performance or security challenges with either approach? Looking forward to your insights!   Looking forward to your insights!

asked 2025-02-13

0 answers