Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage News VMware's CloudFoundry Service Gains Support for PostgreSQL

VMware's CloudFoundry Service Gains Support for PostgreSQL

This item in japanese

Earlier this year VMware released CloudFoundry, an open-source PAAS solution, with initial support for several services such as MongoDB, MySQL, and Redis. Lately it has added PostgreSQL and RabbitMQ to the list of cloud services that applications can depend on, as well as offering a Micro edition of the cloud that can run on a single workstation.

PostgreSQL is an interesting addition since it is a full featured traditional database with a different audience than MySQL or MongoDB users. To accommodate PostgreSQL, cloudfoundry does not use a vanilla version but instead a customized one based on vFabric as explained in the official blog post.

The same post gives an example of using PostgreSQL in a Java project built with Spring Roo. Here we illustrate an alternative approach where the Java application is a Spring based WAR utilizing JPA.

Assume that your application has a Spring context setup as below:

<bean id="entityManagerFactory" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
	<property name="persistenceUnitName" value="myJpaManager" />
	<property name="dataSource" ref="dataSource"/>

<bean class="org.springframework.jdbc.datasource.DriverManagerDataSource" id="dataSource">
	<property name="driverClassName" value="org.postgresql.Driver" />
	<property name="url" value="jdbc:postgresql://localhost/postgres" />
	<property name="username" value="postgres" />
	<property name="password" value="postgres" />

<bean id="transactionManager" class="org.springframework.orm.jpa.JpaTransactionManager">
	<property name="entityManagerFactory" ref="entityManagerFactory" />

<tx:annotation-driven transaction-manager="transactionManager" />
<context:annotation-config />

and a META-INF/persistence.xml like this

<persistence xmlns=""
	<persistence-unit name="myJpaManager" transaction-type="RESOURCE_LOCAL">
		<property name="hibernate.dialect" value="org.hibernate.dialect.PostgreSQLDialect" />
		<property name="" value="update" />

This application can be uploaded to CloudFoundry completely unchanged thanks to the auto-configuration feature of CloudFoundry.

PostgreSQL (as well as MySQL and the rest of supported services) takes advantage of the auto-configuration feature offered by Cloudfoundry. Under certain conditions a local Java Application that uses PostgreSQL can be uploaded to CloudFoundry with zero code changes.

Auto-configuration employs the Spring Core container and takes places when both of the following are true

  1. There may exactly be only one service of a given service type. For example, you may bind only one relational database service (MySQL or PostgreSQL) to an application.
  2. There may exactly be only one bean of the matching type. For example, you may have only one DataSource bean in the application context.

If these requirements hold then Cloudfoundry will automatically intercept your local datasource and use the Cloudfoundry service instead of what is set in the Spring context.

The only thing left to do is to answer positively when vmc asks for service binding when the application is uploaded to the cloud.

For more complex applications, Spring 3.1 is expected to add a special cloud namespace and runtime profile support.

Rate this Article