Wildmoka is a deployed in regional regions. Each Wildmoka platform is independent from the others and is deployed in a Microsoft Azure region:
- apac.wildmoka.com located in Singapore
- central.wildmoka.com located in France
- europe.wildmoka.com located in Netherlands
- south.wildmoka.com located in South USA
- us.wildmoka.com located in East USA
The main services which are used within Microsoft Azure are load balancing, compute resources, kubernetes, cloud storage, and networking services. Wildmoka is designed from the ground up to be highly resilient to failure and every component is chosen to be highly accessible and horizontally scalable.
The Wildmoka platform core is responsible for redundancy, autoscaling and failover within a single region so there are always enough running instances of a particular service to handle the current load and any potential failure. These individual services can be scaled up and down as needed, depending on the current load.
The main database is PostgreSQL, and it is running as an active-passive configuration. Other services such as RabbitMQ and Redis are running as a cluster. Those different configurations are deployed within each individual region to allow for individual machine failures and is backed up to other regions to allow for region failure.
Wildmoka's application layer is composed of different modules running either natively on virtual machines or inside containerized environments like Kubernetes.
Image showing the overview of Wildmoka with third-party integrations
Application monitoring
Wildmoka monitoring is primarily done through Grafana and Loki.
A public page for the current status of Wildmoka is available at https://status.wildmoka.com.
Security
Security is covered by the Security section of this help documentation.