Public vs. Private PaaS

The Platform for the Agile Enterprise

The benefits of using Platform-as-a-Service are clear. Enterprises see their deployment time slashed from weeks to minutes by incorporating one into their application development process.  A PaaS streamlines the process by empowering developers with the ability to deploy their own applications without relying on IT. 
 
However, when deciding whether to use a public PaaS or private one, organizations need to look at a number of dimensions. Each situation is unique, but some general factors such as size of the organization, cost of the system/service, resources to maintain an infrastructure, flexibility required by developers and security/compliance are key considerations in making a decision.
 
Public PaaS
Public PaaS is popular because the developers, and the company in general, don’t have to contend with managing infrastructure in-house. For small and/or medium sized businesses who currently don’t have the resources to manage one, a public PaaS makes sense. Depending on the specific public PaaS selected, additional features such as scaling and monitoring your applications may be available just as it would with a private PaaS. 
 
If the organization is smaller (and possibly in business for a shorter amount of time), they may not require as much flexibility with respect to migrating a large number of legacy applications to the cloud or requiring a wide range of programming languages used to build their applications.  As a result, these organizations may be more suited to using a public PaaS that may support fewer languages and frameworks on their platform.
 
However, two key considerations when evaluating a public PaaS versus a private one are cloud security and compliance. For enterprises and other larger organizations who are faced with these requirements, a private PaaS is generally seen as a better fit for their organization because they may be required to keep their data inside their own firewall on their own private cloud.
 
Private PaaS: Stackato
A private PaaS like Stackato provides the same benefits as a public PaaS—developers can deploy their apps in minutes instead of weeks and significantly streamline the application development process. However, there are additional advantages to Stackato that are beyond what a Public PaaS can provide.
 
Control for IT
Enterprises with strict policies or compliance requirements may be limited to using private clouds. With Stackato, organizations can have the additional security, control, and customization capabilities that they require. In addition, with the use of Docker containers, Stackato ensures that each application has its own security layer so each application is effectively isolated from others residing in the same cloud. This security feature protects them from any malicious activity that another application may be displaying.
 
Freedom for Developers
Similar to the functionality associated with a public PaaS, Stackato gives developers a new freedom—the freedom to deploy their own applications. Developers using Stackato are able to automatically provision the application environment, removing typical configuration management issues such as delays and incorrectly setting up the VM for the application. 
 
In addition, for larger organizations and enterprises who have legacy applications that they want to migrate and require a platform that supports a wider variety of programming languages, Stackato’s polyglot nature may be better suited in this scenario than a public PaaS.
 
 
With each situation, customers need to evaluate what PaaS is right for them. To find out how to give your developers freedom, while IT maintains control, download the Stackato micro cloud and set up your own application platform in minutes.