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

Catherine Edelveis
Catherine Edelveis

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

Tags

BellSoft productsDevelopmentDeployment
Videos
card image
Feb 6, 2026
Backend Developer Roadmap 2026: What You Need to Know

Backend complexity keeps growing, and frameworks can't keep up. In 2026, knowing React or Django isn't enough. You need fundamentals that hold up when systems break, traffic spikes, or your architecture gets rewritten for the third time.I've been building production systems for 15 years. This roadmap covers three areas that separate people who know frameworks from people who can actually architect backend systems: data, architecture, and infrastructure. This is about how to think, not what tools to install.

Watch Now
Videos
card image
Jan 29, 2026
JDBC Connection Pools in Microservices. Why They Break Down (and What to Do Instead)

In this livestream, Catherine is joined by Rogerio Robetti, the founder of Open J Proxy, to discuss why traditional JDBC connection pools break down when teams migrate to microservices, and what is a more efficient and reliable approach to organizing database access with microservice architecture.

Watch Now

Further watching

Videos
card image
Feb 27, 2026
Spring Developer Roadmap 2026: What You Need to Know

Spring Boot is powerful. But knowing the framework isn’t the same as understanding backend engineering. In this video, I walk through the roadmap I believe matters for a Spring developer in 2026. We start with data. That means real SQL — CTEs, window functions, normalization trade-offs — and understanding what ACID and BASE actually imply for system guarantees. Spring Data JPA is useful, but you still need to know what happens underneath. Then architecture: microservices vs modular monolith, serverless, CQRS, and when HTTP, gRPC, Kafka, or WebSockets make sense. Not as buzzwords — but as design choices with trade-offs. Security and infrastructure follow: OWASP Top 10, AuthN vs AuthZ, encryption in transit and at rest, Docker, Kubernetes, Infrastructure as Code, and observability with Micrometer, OpenTelemetry, and Grafana. This roadmap isn’t about mastering every tool. It’s about knowing what affects reliability in production.

Watch Now
Videos
card image
Feb 18, 2026
Build Typed AI Agents in Java with Embabel

Most Java AI demos stop at prompt loops. That doesn't scale in production. In this video, we integrate Embabel into an existing Spring Boot application and build a multi-step, goal-driven agent for incident triage. Instead of manually orchestrating prompt → tool → prompt cycles, we define typed actions and let the agent plan across deterministic and LLM-powered steps. We parse structured input with Ollama, query MongoDB deterministically, classify risk using explicit thresholds, rank affected implants, generate a constrained root cause hypothesis, and produce a bounded containment plan. LLM handles reasoning. Java enforces rules. This is about controlled AI workflows on the JVM — not prompt glue code.

Watch Now
Videos
card image
Feb 12, 2026
Spring Data MongoDB: From Repositories to Aggregations

Spring Data MongoDB breaks down fast once CRUD meets production—real queries, actual data volumes, analytics. What looks simple at first quickly turns into unreadable repository methods, overfetching, and slow queries. In this video, I walk through building a production-style Spring Boot application using Spring Data MongoDB — starting with basic setup and repositories, then moving into indexing, projections, custom queries, and aggregation pipelines. You'll see how MongoDB's document model changes data design compared to SQL, when embedding helps, and when it becomes a liability. We cover where repository method naming stops scaling, how to use @Query safely, when to switch to MongoTemplate, and how to reduce payload size with projections and DTOs. Finally, we implement real MongoDB aggregations to calculate analytics directly in the database and test everything against a real MongoDB instance using Testcontainers. This is not another MongoDB overview. It's a practical guide to actually using Spring Data MongoDB in production without fighting the database.

Watch Now