ShippedJava hosting
on Shipped.
Bring your Java application and its runtime requirements. Shipped provides the infrastructure around the service, from a public URL to connected data.
Keep your existing build process
Package the output of your Maven, Gradle, or other Java build with the runtime it needs. A container makes the JDK or runtime version and system dependencies explicit. Deploy an HTTP application as a web service, or run a separate worker for a program that processes background tasks.
Configure the service for its workload
Java applications need capacity for the whole process, including memory outside the heap. Choose resource settings that fit the application and test representative requests or jobs. Dedicated servers are an option when your service needs its own server capacity, with the infrastructure managed by Shipped.
Keep integrations out of the build artifact
Use secret configuration for database credentials, signing keys, and external service tokens. Connect the deployed service to PostgreSQL or another compatible data service. Separate environment values make it possible to use the same application release in staging and production while each talks to the correct resources.
A little more detail
Questions about Java?
Can I keep Maven or Gradle?
Yes. Use your project’s build process to produce the artifact packaged for deployment. Include the runtime and files the resulting application needs.
Do I need to rewrite a Java app as functions?
No. A Java application can run as a regular service process or worker. Its deployment model should match how the program is designed to run.
From your workspace to the web