The Grassfish platform combines availability and reliability on multiple levels:
Kubernetes
In Kubernetes, liveness and readiness probes monitor the health of the pods.
Failed instances are automatically restarted or removed from the load balance.
Azure Kubernetes Service (AKS)
AKS monitors the nodes and automatically replaces failing nodes.
Application Gateway
Critical services run in multiple replicas behind the Application Gateway. This mitigates the impact of individual instance failures.
Player
The players store assigned content locally:
If the backend or network connection temporarily fails, the players continue playing the existing content.
The display remains functional even during centralized outages.
How long a player can be offline depends on content planning and the frequency of changes. Technically, a longer period is possible.
Note
With the classic VM setup, monitoring is limited to the status of application pools or Windows services.