Spring Boot Thin Jar Builder on MassiveGRID PaaS
The Spring Boot Thin Jar Builder deploys a Java Engine node with Maven and Spring Boot and builds a sample project as a thin JAR, an artefact that contains only your application classes and resolves its dependencies at start-up. It demonstrates a lighter build-and-deploy cycle for Spring Boot microservices on MassiveGRID PaaS.
Both buttons open the MassiveGRID PaaS dashboard with Spring Boot Thin Jar Builder pre-selected. The trial needs no credit card.
Spring Boot Thin Jar Builder Package Facts
| Attribute | Value |
|---|---|
| Package | Spring Boot Thin Jar Builder |
| Type | Application (installs a complete environment) |
| Category | Clusters & Containers |
| Software vendor / project | VMware Tanzu / Broadcom (Spring), Apache Maven |
| Licence | Apache License 2.0 (open source) |
| Runtime / stack | Java Engine node with Maven and Spring Boot, building and running a thin JAR |
| Regions | New York, London, Frankfurt, Singapore |
| Billing | Pay-per-use from $2.46/month ($0.003372/hour), no licence fee |
| Free trial | 14 days, no credit card |
| Uptime SLA | 100% |
What is Spring Boot Thin Jar Builder?
Where a fat JAR bundles every library, a thin JAR (built with the Spring Boot Thin Launcher) ships just your code plus a dependency manifest. On first start the launcher downloads and caches the libraries. Builds are much smaller, uploads and Git pushes are faster, and many services can share a cached dependency set on the same node.
This package installs Maven on a Java Engine node, clones a sample Spring Boot project configured for thin packaging, builds it and starts the service. Swap in your own repository and it becomes a small build server whose artefacts can be promoted to the Spring Boot Cluster.
What the Spring Boot Thin Jar Builder Package Deploys
Marketplace packages are not bare container images. One click provisions a complete, production-shaped environment on MassiveGRID infrastructure.
- Java Engine node: A lightweight Java container with an LTS JDK, sized to its cloudlets.
- Maven and Spring Boot: Apache Maven with the Thin Launcher plugin configured in the sample project.
- Automated thin build: The sample project built into a thin JAR on first deploy, with dependencies resolved and cached at start.
- Running microservice: The service started and exposed over HTTPS on the platform subdomain.
Why Teams Choose Spring Boot Thin Jar Builder
Small artefacts
Thin JARs are typically a few hundred kilobytes rather than tens of megabytes, speeding every deploy.
Shared dependency cache
Libraries downloaded once per node are reused by subsequent builds and services.
Same code, different packaging
Switching between thin and fat packaging is a Maven plugin change, not a code change.
Adaptable template
Replace the sample repository with your own and reuse the node as a build box.
How to Install Spring Boot Thin Jar Builder on MassiveGRID PaaS
Installing the package takes three steps and a few minutes of waiting. No servers to provision, no configuration files to edit.
Open the installer
Click Install with free trial or Install to my account. The MassiveGRID PaaS dashboard opens with the Spring Boot Thin Jar Builder package pre-selected, so nothing has to be copied or pasted.
Sign up or sign in
New to the platform? Sign up for the free 14-day trial, which needs no credit card. Existing customers sign in with their usual dashboard credentials.
Choose region and deploy
Name the environment, pick New York, London, Frankfurt or Singapore, and confirm. The platform builds every Spring Boot Thin Jar Builder node, wires them together and hands you the live URL and credentials.
Who Runs Spring Boot Thin Jar Builder on PaaS
Frequent deployments
Teams pushing many small releases who want fast transfers.
Many microservices per node
Services sharing dependency versions, cached once on the node.
Evaluating thin packaging
Developers comparing thin and fat JAR trade-offs on real infrastructure.
Why Run Spring Boot Thin Jar Builder on MassiveGRID PaaS
Built for uptime. Spring Boot Thin Jar Builder runs on MassiveGRID's high-availability platform, where every environment is covered by a 100% uptime SLA. Nodes live on redundant hosts, storage is replicated, and failed containers are restarted or migrated automatically.
Pay for what you use. Billing is hourly and per cloudlet (128 MiB RAM plus 400 MHz CPU). Vertical auto-scaling adds and removes cloudlets as load changes, so a quiet Spring Boot Thin Jar Builder environment costs a few dollars a month and a busy one grows without a migration. Full details are on the PaaS page.
Your choice of jurisdiction. Deploy in New York, London, Frankfurt or Singapore and keep data inside the region your users or regulators require. MassiveGRID is ISO 9001 certified and GDPR compliant, and has run hosting infrastructure since 2003.
No lock-in. The package is a standard Jelastic Packaging Standard (JPS) manifest. You keep root-level access to the containers, can export the manifest, and can move the workload to any other Jelastic-compatible platform or to your own servers at any time.
Related on massivegrid.com: For Developers.
Spring Boot Thin Jar Builder Questions
More from the Marketplace
Packages that are often deployed alongside Spring Boot Thin Jar Builder, or that solve the same problem a different way. Browse all 84 packages.
Deploy Spring Boot Thin Jar Builder Today
Start the free 14-day trial and have Spring Boot Thin Jar Builder running in minutes. No credit card required.