Spring Boot Fat Jar Builder on MassiveGRID PaaS
The Spring Boot Fat Jar Builder deploys a Java Engine node with Maven and the Spring Boot framework, then automatically builds a sample project into a self-contained fat (uber) JAR and runs it as a microservice. It is a working template for compiling Spring Boot applications from source directly on MassiveGRID PaaS.
Both buttons open the MassiveGRID PaaS dashboard with Spring Boot Fat Jar Builder pre-selected. The trial needs no credit card.
Spring Boot Fat Jar Builder Package Facts
| Attribute | Value |
|---|---|
| Package | Spring Boot Fat 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 fat (uber) 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 Fat Jar Builder?
A fat JAR bundles the application and every dependency into one executable file, which is the standard Spring Boot packaging: simple to run, simple to copy between environments, with no external classpath to manage. The trade-off is size, since each build carries all libraries again.
This package shows the complete build-and-run cycle on the platform. It installs Maven on a Java Engine node, clones a sample Spring Boot project, runs the Maven build to produce the fat JAR and starts it. Point the same node at your own repository and it becomes a build server for your services, whose artefacts can then be promoted to the Spring Boot Cluster.
What the Spring Boot Fat 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 installed with the Spring Boot starter dependencies cached for fast builds.
- Automated build: A sample project cloned and built into a fat JAR on first deploy, so the pipeline is proven immediately.
- Running microservice: The built JAR started and exposed over HTTPS on the platform subdomain.
Why Teams Choose Spring Boot Fat Jar Builder
Source to running service
Compile and run on the platform; no local build tooling or artefact upload needed.
Self-contained artefacts
Fat JARs run anywhere with a JDK, ideal for promotion between environments.
Adaptable template
Change the Git URL and build command to build your own Spring Boot projects.
Pay only while building
Stop the node between builds with the Start/Stop Scheduler and pay nothing for idle time.
How to Install Spring Boot Fat 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 Fat 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 Fat Jar Builder node, wires them together and hands you the live URL and credentials.
Who Runs Spring Boot Fat Jar Builder on PaaS
Learning Spring Boot deployment
Developers who want to see a real build-and-run cycle on cloud infrastructure.
Lightweight build servers
Small teams building JARs from Git without a full CI server.
Prototype microservices
Quickly turning a repository into a running HTTPS endpoint for demos and testing.
Why Run Spring Boot Fat Jar Builder on MassiveGRID PaaS
Built for uptime. Spring Boot Fat 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 Fat 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 Fat Jar Builder Questions
More from the Marketplace
Packages that are often deployed alongside Spring Boot Fat Jar Builder, or that solve the same problem a different way. Browse all 84 packages.
Deploy Spring Boot Fat Jar Builder Today
Start the free 14-day trial and have Spring Boot Fat Jar Builder running in minutes. No credit card required.