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? ;)
VMware launches Node.js, Rails and Spring PaaS
41–50 of 57 posts
Re: VMware launches Node.js, Rails and Spring PaaS
#42Earlier quoted context omitted.
We can take any .war file that runs on Tomcat, even jruby apps. Not just spring.
I really think you should make this clear. We're a Java shop, but we use all sorts of frameworks; play, spring, homegrown, but they all build to .war. This is an interesting product to me, but from the marketing material it's not obvious...
Also look for some more technical deep dive blog posts on my blog by tomorrow at http://brainspl.at where I will clarify a bunch of this stuff.(right after I get some sleep;)
Re: VMware launches Node.js, Rails and Spring PaaS
#43It 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.
Their core business today is selling vSphere 4 management with ESXi as the hypervisor, I think they see their core business in 10 years as being the management layer for your entire IT infrastructure, wherever it runs.
Re: VMware launches Node.js, Rails and Spring PaaS
#44Earlier quoted context omitted.
When was the last time Heroku accepted a pull request from you? ;)
As a follow up, my initial response came out a bit more snarky than I intended. Sorry about that.
This project means to take it further though and be one everyone's cloud operating system, the Linux of cloud OS's if you will. It will live or die based on the open source can build around it. I fully intend to try to build this community and nurture it so this project flourishes. The personal PaaS angle is what I'm most excited about. Whatch for my technical blog posts tomorrow after I get some rest for more info...
Re: VMware launches Node.js, Rails and Spring PaaS
#45What do they mean by "Spring applications"? That's quite obscure. Do they mean they handle .war J2EE applications? Or they only support Spring libraries?
We can take any .war file that runs on Tomcat, even jruby apps. Not just spring.
Re: VMware launches Node.js, Rails and Spring PaaS
#46I 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.
Re: VMware launches Node.js, Rails and Spring PaaS
#47Re: VMware launches Node.js, Rails and Spring PaaS
#48I 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.
Virtualization isn't the only way to isolate apps. What happened to good old Unix user accounts? It seems ridiculous to me to allocate entire kernels and OS runtimes per user/app when they can just share all that stuff and have the kernel isolate access and divide resources.
Re: VMware launches Node.js, Rails and Spring PaaS
#49I 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.
Shared hosting is now called "Multi-tenant", and that is how Heroku, Google Appengine, Windows Azure and other multi-tenant PaaS hosters work. Their thousands of users don't seem to mind.