Scaling our Quarkus service
So far, you've learned how to deploy a Quarkus application on Minishift. The application is running in a Pod, which is allocated in its own internal IP address and is the equivalent of a machine running a container. In our case, the application is running on one Pod in an OpenShift node. This is sufficient to guarantee the availability of our applications since some liveness and readiness probes are periodically executed. If your Pods stop responding, the OpenShift platform will automatically restart them.
On the other hand, your application probably needs to satisfy a minimum throughput. This requirement usually can't be met with just one Pod unless the number of requests is pretty low. In this case, the simplest ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access