node.js and Cloud Foundry

January 24, 2012 Cloud Foundry

featured-cf-genericCloud Foundry is a sponsor and participant in this week’s Node Summit in San Francisco, so it is a good time to recap some of our work with node.js.

We’re finalizing node.js 0.6.7 support, which will be committed to the Cloud Foundry GitHub repository. Cloud Foundry.com will begin to support node.js 0.6.7 as a runtime framework in the next week or two. Because of the rapid pace of innovation around node, we are adding node.js 0.6.7 as an additional runtime, letting you select which version of node you want to run with your application. This lets Cloud Foundry support multiple node.js versions simultaneously, which is important as it allows applications written against the node.js 0.4.12 version to co-exist with applications developed on node.js 0.6.7.

This work represents the first fruits of our partnership with Joyent, who is the Cloud Foundry Community Lead for node.js. Going forward, we will have a joint open source engineering model with Joyent that lets the Cloud Foundry, node.js, and Redis teams all work together to deliver a highly optimized PaaS solution across those components.

The next few months should be big for node.js and the community around it. Modern applications are becoming more demanding, diverse, and complex. We see node.js as a great fit in addressing many of the problems posed by this. A few examples of the efforts going into leveraging node.js with Cloud Foundry are covered in the links below.

  • The Cloud Foundry Team

Don’t have a Cloud Foundry account yet? Sign up for free today

About the Author

Biography

More Content by Cloud Foundry
Previous
Multi-Language, Multi-Framework, what about Multi-Cloud?
Multi-Language, Multi-Framework, what about Multi-Cloud?

Previously, developers had to put a lot of energy into preserving choice across operating systems and minim...

Next
Unwanted whitespace between elements
Unwanted whitespace between elements

We recently came across a situation in our markup where we wanted whitespace in the markup for readability,...