Five things to consider before moving legacy development efforts to PaaS
Grazed from TechTarget. Author: Dan Sullivan.
Platform as a Service offers advantages over managing your own development infrastructure and allows more time to focus on designing and coding. While PaaS may be the preferred choice for new projects, it may not be a good fit for existing, legacy development efforts. Here are five things to consider before moving your legacy development projects to Platform as a Service (PaaS).
1. How will you use PaaS?
Different companies have different uses for PaaS to suit their IT environments and goals. First you must figure out how to incorporate PaaS into your organization. Some services allow you to move computation easily to the cloud while maintaining other functions on local resources. For example, Pi Cloud provides an application program interface (API) for copying your local Python code to the cloud and running it there, while your development tools and code repositories can stay local…


The OpenStack Foundation issued its Grizzly release Thursday with 230 new features for running production-level cloud computing, but the most important additions dealt with the new area of software-defined networking. The OpenStack compute component can now support multiple hypervisors, including VMware ESX Server, open source KVM and Xen and Microsoft’s Hyper-V. "With Grizzly, there’s no advantage of one hypervisor over another," said John Engates, CTO of Rackspace, the cloud services supplier that first got the OpenStack project going in collaboration with NASA. OpenStack has been known up until the Grizzly release for primarily supporting KVM, the open source hypervisor that’s found inside the Linux kernel and often favored by open source developers.
Who is Amazon’s biggest competitor in the cloud? The go-to answer for many may be companies like Rackspace with its OpenStack platform, perhaps Google with its Compute Engine, Microsoft Azure, VMware or one of the up-and-coming cloud computing companies like Joyent.