Cloud Foundry faces fear of forking

donjduncan:

Interesting thoughts and I agree Forking can be beneficial in different circumstances especially when technology is not evolving at the pace it should.

Originally posted on Gigaom:

The rumblings have been around for weeks but now they’re breaking the surface: Cloud Foundry, the open source platform-as-a-service framework faces a bit of an insurrection. Several vendors, such as AppFog, ActiveState, Tier 3, Uhuru, etc. — have built PaaSes atop the framework and some have quietly been mulling forking the Cloud Foundry code, citing lack of clarity about the project’s future.

cloudfoundrylogoThe attraction of the multi-vendor Cloud Foundry effort is that, in theory, it would provide customers an array of compatible PaaSes from different vendors. If they don’t like their experience with one, they can move their code elsewhere. But now the prospect of a “fork” looms with some other vendors thinking of splitting off and doing their own iterations. Worst case scenario: that could negate any promise of compatibility. And that raises the old bugaboo of vendor lock-in which even PaaS providers say has restricted business…

View original 396 more words

About these ads

About donjduncan

Application/Technology Sales Engineer: BYOD,Cloud,Virtualization,Application Transformation,Mobility,Process,and Automation. Currently looking for new opportunities. Linkedin: http://www.linkedin.com/in/donjduncan Twitter: donjduncan
This entry was posted in cloud computing, PaaS and tagged , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s