Running Standalone Web Applications on Cloud Foundry

by May 11, 2012

In this final post of the four-part series on deploying standalone apps to Cloud Foundry, we will explore how to build and deploy JVM-based web applications that aren’t packaged as traditional WAR files. This includes applications that are built on top of an NIO Framework like Grizzly or Netty (notable frameworks include Blue Eyes and vert.x) and applications that ship their own container, such as an embedded Jetty server.

Also in this series:

Cloud Foundry Improves Support For Background Processing

Running Resque Workers on Cloud Foundry

Running Workers on Cloud Foundry with Spring

Deploying a Spray Application to Cloud Foundry
Spray is a suite of lightweight Scala libraries for building and consuming RESTful web services on top of Akka.

Cloud Foundry Improves Support For Background Processing

by May 1, 2012

Cloud Foundry has significantly enhanced support for worker applications that perform background processing by allowing applications to run on without the application container. Cloud Foundry applications are no longer limited to Web applications that respond to HTTP requests. Instead, they can be run as executable or “standalone” applications. A standalone application is one that does not require a provided framework or container.
Many developers create distributed applications that have workers to perform specific functions and communicate via a data or messaging system, such as those developed with Spring Batch, Spring Integration, Resque, or Delayed Job.