In 2016, all development teams are now converted to agile methods and large enterprise now have genuine software production plants to deliver power at faster applications and new versions required by the business. This race to the agility and speed of execution makes Platform as type of service has interesting service on several aspects. On the one hand the PaaS enables faster Release and face the vagaries of the scalability of applications. In addition, PaaS service publishers offer not only the support of the major languages of the market but also development frameworks that greatly facilitate the creation of new applications.
Two types of PaaS for both needs
Some cloud solutions address even directly to business experts, using online tools and simplified programming languages can quickly create applications that meet their expectations. These graphical construction tools are designed to implement functional blocks offered by the cloud provider. Experts call these solutions “Model-Driven PaaS”, ie PaaS platforms based on a modeling approach. These services clearly aimed at business users with little experience in encoding application.
Other platforms are destined more developers and DevOps teams. These are the “Deployment PaaS” or PaaS platforms oriented deployment. These services offer today all the key bricks of an IT architecture: databases, languages, application servers, etc.
Attention to technical adherence platforms
In one case a case like the other, the gains from these Paas in terms of agility and implementation flexibility make them very attractive to companies looking for speed but it is necessary to take some precautions in the choice the service. Some services have a functional scope is restricted there is a PaaS-oriented business, and some Paas implement proprietary technologies. ” We need to focus on the adhesion of the PaaS platform because it varies from one service to another ” estimates Julien Corioland, technical evangelist for Microsoft Azure offers . ” If we take the example of a solution like SQL Azure Database, this is strictly the same as SQL Server software that can be installed on any server. The only thing that will be brought to modified for applications that use the cloud service, it will be the connection string to the database. ” The relational engine is iso-functional, whether in the cloud or on a server on-premise, portability is complete.
Similarly, the hosting of Web applications on Azure Web App, be it a .NET application, Node.js, PHP, Ruby, Python or Java poses no major problem of portability. ” As long as the code is not specific, there is no adhesion to the platform and change Paas provider will not cause any problems from this point of view. ” said Julien Corioland. ” Where it becomes more complex, it’s actually when using specific solutions to a platform and there is no direct equivalent to an on-premise deployment or other PaaS services. ”
To enjoy the undeniable gains from the Cloud without ending up bound hand and foot with a supplier, a phenomenon of ” vendor lock-in ” affectionately by some providers, you should opt for cloud services that support the languages and databases well-established market data that is known to be able to find other cloud providers or retain the ability to deploy the same solutions on an internal cloud, if any.
As for application development frameworks offered by suppliers, again make sure their universality and, if it is not possible to find equivalents in other solutions, evaluate the pros and cons to leverage these proprietary solutions.