Announcing Heroku Enterprise for Java
Posted about 3 years ago by Sara
A year ago we we launched Java support with the ability to deploy Maven based Java applications using Heroku’s familiar git based workflow. Many customers, like Banjo, have since taken advantage of the new capabilities and built a wide variety of Java applications on the platform.
With the introduction of Java support, we are seeing growing interest from larger enterprises who are often heavy Java users and who are looking for a platform like Heroku to increase the speed of application delivery.
Today, we are announcing Heroku Enterprise for Java, a new product that makes it simpler than ever for enterprise developers to create, deploy and manage Java web applications using their preferred tools and processes. The product is priced at a monthly subscription fee per production application making it easy for the business to align investment with value.
Let us look at the features in detail.
Full stack Java
The vast majority of Java web apps use a baseline set of components: A JDK, a Tomcat web app container, a SQL database and a caching layer to handle session state. Heroku Enterprise for Java includes these baseline components, pre-configured and pre-integrated out of the box.
OpenJDK 6, 7 or 8
You can choose the Java environment that you need whether it is version 6, 7, or the upcoming OpenJDK 8. Read more...
Tomcat 7 web app container
The open source Apache Tomcat container is the most popular way to run Java web applications. Heroku supports Tomcat 7 deployment through WAR files and Maven builds. Read more...
Memcache backed distributed HTTP session state
For maximum scalability Heroku applications can use a Memcache store for distributed session state. This alleviates the scalability limitations associated with typical session replication strategies. Externalized session state alleviates memory and replication overhead while providing durability across application updates. Read more...
Production Heroku PostgreSQL database
Heroku Enterprise for Java includes a Heroku Postgres production database because almost every Java web application stores data in a SQL database. Read more...
Built-in best practices for rapidly deploying new application versions
Deploy and Test - then Promote
With Heroku Enterprise for Java you can instantly deploy Java web apps to staging environments where those applications can be tested and then promoted to production. This provides a major simplification over the usual deployment workflows for enterprise apps.
Continuous Integration Plug-in for Atlassian Bamboo
Heroku Enterprise for Java enables automated deployment of tested applications (i.e. Continuous Delivery) through a plug-in for Atlassian's Bamboo CI solution. Read more...
Dynamic Runtime Environments
Create and scale complete, self-healing environments
Managed and instantly scalable environments for production and staging
A key enabler for continuous delivery is the ability to seamlessly provision and manage many different environments. This is a core feature of the Heroku platform where a new environment can be brought up with a simple
heroku create. Heroku Enterprise for Java includes a full set of development, testing, staging and production environments that can be easily manipulated from the Eclipse IDE, web interface or command line tool.
Native Java Tools
Heroku Enterprise for Java works with tools you know and trust
Eclipse-based development using the new Heroku Eclipse plug-in
For developers who use IDE workflows the new Heroku Eclipse plug-in makes it easy to create, deploy, and manage their Heroku apps entirely within Eclipse. Read more...
WAR based deployment of Java web apps
Java web applications are often packaged into WAR files and deployed to a container. Heroku now supports the deployment of WAR files to a Tomcat 7 container from the command line and from Eclipse. Read more...
Enterprise-grade applications need enterprise-level support. Heroku Enterprise for Java includes SLA based support over tickets or email for quick resolution of deployment or operational problems.