AlmaLinux serves as a replacement for us; initially, we were using CentOS because we had a couple of Red Hat servers as well, but Red Hat operates on a licensing model, whereas CentOS was a free open source component. When CentOS was discontinued, we moved to a different solution, but we believed AlmaLinux could be the right replacement. We have a couple of use cases for AlmaLinux. On AWS, we have a couple of EC2 instances running AlmaLinux, which we mostly use for application servers. We host applications such as Apache and NGINX and similar components. I can confirm that for one of our Kubernetes worker nodes, we also used AlmaLinux, but not for all, only for one or two worker nodes to conduct some research and development.
We have a couple of static websites running on AlmaLinux, mostly for our own Wikipedia-like content and to host knowledge-based articles and internal company, team, and project information. We have Apache servers running on top of AlmaLinux, and those Apache servers connect with databases. Those databases come directly from Amazon RDS. That is our main use case. Another use case is the Kubernetes worker node. We have a custom Kubernetes deployment on AWS, not the Amazon-provided Kubernetes. In that custom Kubernetes solution, we have deployed AlmaLinux as the operating system for the worker nodes. This also proves helpful, as we have containers, pods, and other services running on top of the worker nodes.
We have used AlmaLinux for database servers, but that did not work as well because we need good scalability and reliability. We conducted a small proof of concept with that, and if the scale is very low, then it is good. However, if we need high scalability, then we will definitely have to switch and deal with some other database solutions. I would say this is also good for databases.