About This Architecture

usBIM on-premises Kubernetes platform combines a hardened Kubernetes 1.31+ cluster with specialized BIM microservices, multi-database backends, and Windows Server compute nodes for IFC/Revit processing. Traffic flows through MetalLB load balancer to Traefik ingress controller, which routes requests to containerized services including usbim-platform-api, usbim-cloud document management, usbim-browser viewer, and integration services, all orchestrated via ArgoCD GitOps. PostgreSQL, MongoDB, Neo4j, and ScyllaDB provide polyglot persistence, while Vault secures secrets and PKI, Harbor manages container images, and RustFS S3-compatible storage handles BIM file artifacts. This architecture demonstrates production-grade on-premises Kubernetes for complex domain applications requiring hybrid Linux/Windows workloads, certificate automation, and enterprise security controls. Fork and customize this diagram on Diagrams.so to adapt the topology for your infrastructure, adjust resource allocations, or integrate additional middleware services. The design balances high availability through multi-replica control planes and worker nodes with operational simplicity via Helm, Terraform, and GitOps automation.

People also ask

How do you design a production on-premises Kubernetes cluster for BIM applications with Windows Server processing nodes and enterprise security?

This diagram shows a complete Kubernetes 1.31+ architecture combining Linux control plane and worker nodes with Windows Server hosts for IFC/Revit processing, secured by Vault PKI and Cert-Manager, load-balanced via MetalLB and Traefik, and deployed via ArgoCD GitOps. Multi-database backends (PostgreSQL, MongoDB, Neo4j, ScyllaDB) support polyglot persistence, while Harbor and External Secrets Oper