Live data from Hacker News

VMware launches Node.js, Rails and Spring PaaS

cloudfoundry.com

21–30 of 57 posts

Re: VMware launches Node.js, Rails and Spring PaaS

#21
post #7

This seems fine for fun apps or testing, but I would be incredibly concerned to agree with these terms of service if I was running production software or charging for it. From their terms of service: b. Your Applications and Code. If You create online applications or program code using the Service, You authorize Cloud Foundry to host, copy, transmit, display and adapt such applications and program code, solely as nec…

Seems reasonable to me. I think terms like this are essential elements for a PaaS offering.

Re: VMware launches Node.js, Rails and Spring PaaS

#22

Earlier quoted context omitted.

It also supports multiple frameworks/languages.

Technically, so does Heroku. CloudFoundry does offer Java support, which is a bit different. I am interested to see how it looks once it gets out of beta. I am betting it will be a solid platform, but after seeing the demo a few months ago at RubyConf, it did feel like a model I had seen before.

When was the last time Heroku accepted a pull request from you? ;)

Re: VMware launches Node.js, Rails and Spring PaaS

#23

It definitely makes sense for VMware to build and open source this, since their core business is selling the virtualization software this runs on top of (I assume). Though I wonder how much of it is really VMware specific, or if it would be relatively easy to port to Xen, etc. Edit: actually it appears it might be agnostic to the virtualization layer.

It doesn't care about virtualization layer, runs on raw hardware too.

Re: VMware launches Node.js, Rails and Spring PaaS

#24

No price given. I'll keep using AppEngine until someone at least comes close to matching their freemium model.

Preso just ended, small update: there will be both free + pay service. For now, everything free. So we still don't have details, but we know the model they are pursuing.

Re: VMware launches Node.js, Rails and Spring PaaS

#25

"the industry’s first open platform as a service". First? How is this different from Heroku and other such folks?

It doesn't seem like its different people from Heroku. If you've seen Mark Benioff's cloudforce pitch (link below), he mentions that they're partnering with VMWare to launch a PaaS similar to Heroku (which they acquired in December). That said, I think its a bit surprising that VMWare is launching this under their branding - the machinations of large corporations continuously confound me. http://www.salesforce.com/vi…

according to the register: http://www.theregister.co.uk/2011/04/12/vmware_open_sources_...

"Cloud Foundry serves as the basis for the VMforce platform cloud VMware is building in tandem with Salesforce.com. Therefore, Chen tells us, developers will be able to readily move applications between VMforce and other Cloud Foundry services"

So they are both apparently releasing differently branded versions of the same stack.

There is no history in the git repos, so not clear if any of the code comes from Heroku.

Re: VMware launches Node.js, Rails and Spring PaaS

#26

Earlier quoted context omitted.

Technically, so does Heroku. CloudFoundry does offer Java support, which is a bit different. I am interested to see how it looks once it gets out of beta. I am betting it will be a solid platform, but after seeing the demo a few months ago at RubyConf, it did feel like a model I had seen before.

When was the last time Heroku accepted a pull request from you? ;)

Hey there, Ezra! :)

Agreed...the open aspect of it and how it morphs through the community will be very interesting. Looking forward to it.

Re: VMware launches Node.js, Rails and Spring PaaS

#30
post #17

I was suprised no virtualisation is included in the solution (or I did not find the parts in the github repos). Seriously, shared-hosting is so 1996 from a security perspective. So for me It will be "just" an "internal cloud" solution and maybe replace capistrano. Still, puppet and chef will do the "physical"/"system" provisioning for my customers and my projects.

As far as I can make out so far it is not designed to be multitenant. Each client gets an instance for their apps which can consist of multiple VMs. Based on interpreting the install guide here https://github.com/cloudfoundry/vcap
Post reply on HN