Liberica JDK with CRaC Support

What is CRaC and how does it work?

CRaC or Coordinated Restore at Checkpoint is a Checkpoint/Restore API to pause a running application at an arbitrary point in time (“checkpoint”), save the checkpoint file (snapshot), and then restore the state of an application from the file.

CRaC works like a “save button” for your application and allows you to “load” it next time you start it in the state of your choice.

In addition, CRaC API can perform essential preliminary tasks, such as closing network connections and open file descriptors, and then return to normal operation after restore and react to possible changes in the environment since the checkpoint.

CRaC technology requires a compatible Linux OS which we also provide in the form of Alpaquita Linux. For easier integration we also offer production-ready containers, featuring Liberica JDK with CRaC support and Alpaquita Linux.

Read our article to find out more

Liberica Runtime Containers with CRaC Support

For convenient integration, we offer a ready-to-use Liberica Runtime Container featuring Liberica JDK with CRaC support and Alpaquita Linux.
With CRaC, startup and warm-up times are minimized to near zero, ensuring services start at peak performance. This makes scaling and resource planning easy, precise, and predictable.
You can add precisely as many instances and as much memory as needed to run your Java services as the load increases. There's no need to allocate extra resources for Java startup or warm-up.
Thus, CRaC helps achieve higher availability at lower costs.

Find out more about testing