Boost The Performance and Security of Your Spring Boot App with Alpaquita Containers

Transcript

Imagine running your Spring Boot app in a container that boosts both performance and security.

With Alpaquita Containers you don't have to compromise. They are small, fast and designed with security in mind. Just update the ‘FROM’ line in your Dockerfile, and you are ready to go.

Hi, I'm Cat, developer advocate at BellSoft. Let's talk about why you should switch to Alpaquita Containers. And here are five reasons for doing that.

Reason 1. Performance optimizations

By switching to Alpaquita Containers, your Spring Boot app can use up to 30% less RAM and disk space. How? Alpaquita Containers are based on Liberica JDK Lite, a flavor of Liberica JDK.

It was built specifically for cloud deployments. And by the way, Liberica JDK is recommended by Spring. Alpaquita Containers also come with a lightweight Linux distribution called Alpaquita.

This is the only Linux optimized for Java. And it supports both musl and glibc libraries.

Reason 2. Security

Alpaquita Containers were built with security in mind. The Alpaquita Linux security is hardened

with Secure Boot support, minimal extra packages in userspace, special userspace compilation options and other security features. Additionally, Alpaquita Containers are continuously updated to patch known vulnerabilities.It means that every time you rebuild your container image,

you can be sure that Alpaquita Containers are based on the latest JDK and Linux version with fixes for known CVEs. And the best part? You don't have to manually update the container.

Simply use the ‘latest’ tag, and the newest, most secure image will be pulled automatically for you.

Reason 3. 100% Open-source

Alpaquita Containers are 100% open source and free for commercial and personal use.

BellSoft also provides technical support with SLAs for enterprises with strict security requirements.

Reason 4. Available as buildpacks

Alpaquita Containers are available as buildpacks. If you prefer buildpacks to Dockerfiles,

Alpaquita's buildpacks help you build smaller images without additional configuration.

It's easy, just specify the builder in your Maven or Gradle plugin, and build small container images with just one line of code.

Reason 5. Further performance optimization

If you are looking to reduce startup and warm-up times, cut cloud costs and improve scalability, Alpaquita Containers support tools for that, such as AppCDS, GraaLVM native image, and the Coordinated Restore at Checkpoint (CRaC) project. I have written dedicated blog posts about these solutions on Bellsoft's blog. Check it out and subscribe for tips on performance, security and all things Java. And that was quick overview of why you should switch to Alpaquita Containers when containerizing Spring Boot applications. Migration is super easy. Just update the ‘FROM’ line in your Dockerfile, and that's it. Try Alpaquita Containers today. The links are in the description box below. That was me, Cat from BellSoft. We provide the most complete Java experience. See you next time!

Summary

Alpaquita Containers offer a secure, high-performance solution for running Spring Boot applications in the cloud. These lightweight containers, built on Liberica JDK Lite and Alpaquita Linux, optimize memory and disk usage, reducing resource consumption by up to 30%. Designed with security in mind, they provide automatic updates to patch vulnerabilities and ensure the latest fixes. Fully open-source and available as buildpacks, Alpaquita Containers support advanced tools like AppCDS and GraalVM for further performance enhancements, making them easy to adopt by simply updating the ‘FROM’ line in your Dockerfile.

About Catherine

Java developer passionate about Spring Boot. Writer. Developer Advocate at BellSoft

Social Media

Videos
card image
Oct 24, 2024
5 Tips for Optimizing Java Performance on Kubernetes

If your Java apps in the cloud struggle with high resource consumption, frequent container restarts, or slow response times, these five tips can help enhance their performance. First, set CPU and RAM limits properly based on load testing and account for Kubernetes overhead.

Videos
card image
Oct 21, 2024
Why Test Performance When Scaling K8s

Running the HotSpot JVM in containers requires careful tuning of resource limits, garbage collection, and JVM options to maximize performance and avoid issues like container restarts or poor scaling.

Further watching

Videos
card image
Nov 29, 2024
OpenJDK Projects That We Anticipate

OpenJDK is actively evolving, with projects like Leyden, Valhalla, Babylon, and Lilliput aiming to enhance Java's performance and capabilities. Leyden focuses on faster startup and warmup by reusing precompiled code, while Valhalla introduces value objects, primitive classes, and specialized generics for better memory and runtime efficiency.

Videos
card image
Nov 22, 2024
Reducing Java Startup Time: 4 Approaches

Java application startup can be significantly accelerated using modern tools. AppCDS stores preloaded classes in a shared archive, cutting startup time by up to 50%, while Project Leyden shifts optimizations to earlier stages with ahead-of-time compilation. GraalVM Native Image creates standalone executables for sub-second startup, and CRaC restores pre-warmed application states for instant readiness.

Videos
card image
Nov 1, 2024
An Overview of Java Garbage Collectors

Java provides multiple garbage collectors (GCs) tailored to different performance needs. Serial GC is ideal for single-threaded apps but pauses all threads, while Parallel GC uses multiple threads to prioritize throughput.