Midaz is designed for genuine portability and independence; you can deploy it on any public or private cloud without being tied to a single provider.Underneath, we utilize a microservices architecture, which allows each component to be self-sufficient and easily scalable (or replaceable) as your requirements change.
This layer is managed by the customer and provides the Kubernetes foundation for running Midaz. We recommend enabling the following services to ensure a smooth and secure deployment:
Service: Networking abstraction to expose and route services.
AutoScaler: Automatically adjusts the number of pods.
HPA (Horizontal Pod Autoscaler): Scales applications based on metrics.
Secrets: Secure management of sensitive data.
ConfigMap: Externalized configuration management.
This layer governs and coordinates all components within the cluster.
Midaz uses Helm Charts (specifically lerianstudio/helm) to make infrastructure deployment and configuration more straightforward and efficient.It serves as the connecting element between code and Kubernetes, ensuring each component is deployed consistently across different environments.
In Midaz’s Architecture, each layer is focused, with no unnecessary complexity. It scales naturally and adapts as your needs change. This setup isn’t just technically solid; it’s built for real-world use.
Kubernetes coordinates how each layer communicates, ensuring secure and reliable interactions across the system.
Helm keeps deployments and configurations in sync, so scaling and updates happen without friction.
Because the platform is modular, extending it is simple. You can add new components as needed without disrupting what’s already in place.
