Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×
Cloud

+ - Which PaaS Is Best For Legacy Java Apps?->

Submitted by
snydeq
snydeq writes "Andrew C. Oliver and Lifford Pinto detail the ups, downs, ins, and outs of deploying a legacy Java application to 7 leading platform-as-a-service clouds, including Amazon Elastic Beanstalk, CloudBees, Google App Engine, Heroku, Microsoft Azure, Red Hat OpenShift, and VMware Cloud Foundry. The writeup includes a look at key differentiating features, lock-in, security, and the kinds of companies using each PaaS. 'It's still a bit early in the PaaS space, but you can already begin porting legacy apps to some cloud platforms with only minor changes or possibly none at all. Big companies and small companies alike may find a PaaS to be a compelling way to deploy applications and cut capital expenditures. This market isn't as crowded as it might seem, as many of the big players aren't yet out of beta. But in the coming months we can expect that to change.'"
Link to Original Source
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

Which PaaS Is Best For Legacy Java Apps?

Comments Filter:

"An organization dries up if you don't challenge it with growth." -- Mark Shepherd, former President and CEO of Texas Instruments

Working...