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…

Another option is to develop with on-premises resources and test with a PaaS product. This approach is useful when you run a large test suite or need separate instances of shared resources to test properly. You can also move all your development to the cloud by using a cloud integrated development environment (IDE). Review the features supported by browser-based IDEs — some are lightweight and may not have all the features you may be accustomed to…

Read more from the source @ http://searchcloudcomputing.techtarget.com/tip/Five-things-to-consider-before-moving-legacy-development-efforts-to-PaaS