Scalability is crucial, allowing applications to grow without disruption. Integration with existing systems enables seamless operation across platforms. A developer-friendly environment ensures ease of use and accelerates development cycles. Security features protect sensitive data and ensure compliance with regulations.
Cost-effectiveness balances initial and ongoing expenses against potential benefits, making budget management easier. Performance monitoring tools help maintain application efficiency and detect issues early. Having robust features ensures that the platform supports both technical and business requirements, offering flexibility and reliability.
One of the considerations is security controls of Company specific information flowing in and out with the Platform being in the cloud and how is the consistency and reliability and bandwidth of the network traffic for heavy peaks usage.
With our organization trending towards a Micro Services based Architecture we look at ease of integration with on premise capabilities as well as the provider footprint.
I can see that our fellows raised important aspects... So I would like to issue another:
Your organizational control over application.
Once you are putting your data in a SaaS, mostly, you are not in charge any more...
- If you want to take your data away, it's a problem.
- If you don't agree to a price raise, what are your options?
- If an platform (SaaS) upgrade will force you to invest in compatibility in their time table - you are forced.
So, the issue I'm raising is portability between providers.
One possible way of implementing portability, is that the SaaS provider will not own the other layers (IaaS, PaaS)
1) What happens to the data? I am responsible for the data of our customers!
2) How can I do the necessary IT Service Management? We've put a lot of Governance in the Operations of our IT-Services. This is part of the value of those services and one of the reasons why our customers trust ust.
I think it is important to evaluate how easy/difficult it is to migrate from whatever current system you are using (PaaS or not) and the target PaaS. It is also important to look at how easy/difficult it is to divorce your users/systems from the target PaaS should your Company purchase a different platform in the future.
Security, security, security. As Peter Loudon mention further above, the ease of integration does not matter to me, our Dev teams can virtually integrate everything with anything.
Control over our data is at place 2 and scalability ranks on 3rd place!
Standards Wonk at a tech company with 10,001+ employees
Real User
2014-10-13T18:39:55Z
Oct 13, 2014
More than either SaaS or IaaS, PaaS systems vary in the level of abstraction they provide their consumers. There are lower-level PaaS systems, like Elastic Beanstalk, and higher-level PaaS systems, like Heroku. There are trades off between efficiency, on one hand, and control, on the other. You need to find the most efficient system that still allows you enough control to do what your app needs to do. The other consideration is whether or not the PaaS system provides the services your app needs. Do you need message queueing, log aggregation, traffic analytics, etc.? It's good if there are multiple providers of the services you need in the ecosystem of the PaaS you intend to use.
In the wake of NSA revelations, security has become the number 1 issue.
Prior to that (and now second to security) is the degree to which it will integrate seamlessly with the rest of the enterprise platform, the speed and resilience of internetworking (in Africa this is huge), and the extent to which the platform is redundant, backed up and under my control for configuration purposes.
A free trial (without a credit card or a phone call) and clear pricing details are the important aspects that I look for while purchasing PaaS solutions.
The maturity of the API stack is important. The need for an API stack that takes into account private/hybrid cloud implementations is important (enterprise perspective).
Availability of an easy to use Web interface to monitor and control the PaaS that should be able to run a Java WAR that runs locally without any change or constraint.
PaaS Clouds provide a strategic way to develop, run, and manage applications without dealing with infrastructure complexities. Offering scalability, developers focus on coding while platforms handle backend processes.Offering a highly flexible environment, PaaS Clouds allow developers to use pre-configured systems, minimizing setup time and speeding up the development process. They focus on delivering robust solutions suited for modern tech landscapes. Incorporating features like integrated...
Key features to look for in PaaS Clouds include:
Scalability is crucial, allowing applications to grow without disruption. Integration with existing systems enables seamless operation across platforms. A developer-friendly environment ensures ease of use and accelerates development cycles. Security features protect sensitive data and ensure compliance with regulations.
Cost-effectiveness balances initial and ongoing expenses against potential benefits, making budget management easier. Performance monitoring tools help maintain application efficiency and detect issues early. Having robust features ensures that the platform supports both technical and business requirements, offering flexibility and reliability.
One of the considerations is security controls of Company specific information flowing in and out with the Platform being in the cloud and how is the consistency and reliability and bandwidth of the network traffic for heavy peaks usage.
With our organization trending towards a Micro Services based Architecture we look at ease of integration with on premise capabilities as well as the provider footprint.
I can see that our fellows raised important aspects... So I would like to issue another:
Your organizational control over application.
Once you are putting your data in a SaaS, mostly, you are not in charge any more...
- If you want to take your data away, it's a problem.
- If you don't agree to a price raise, what are your options?
- If an platform (SaaS) upgrade will force you to invest in compatibility in their time table - you are forced.
So, the issue I'm raising is portability between providers.
One possible way of implementing portability, is that the SaaS provider will not own the other layers (IaaS, PaaS)
1) What happens to the data? I am responsible for the data of our customers!
2) How can I do the necessary IT Service Management? We've put a lot of Governance in the Operations of our IT-Services. This is part of the value of those services and one of the reasons why our customers trust ust.
I think it is important to evaluate how easy/difficult it is to migrate from whatever current system you are using (PaaS or not) and the target PaaS. It is also important to look at how easy/difficult it is to divorce your users/systems from the target PaaS should your Company purchase a different platform in the future.
Security, security, security. As Peter Loudon mention further above, the ease of integration does not matter to me, our Dev teams can virtually integrate everything with anything.
Control over our data is at place 2 and scalability ranks on 3rd place!
More than either SaaS or IaaS, PaaS systems vary in the level of abstraction they provide their consumers. There are lower-level PaaS systems, like Elastic Beanstalk, and higher-level PaaS systems, like Heroku. There are trades off between efficiency, on one hand, and control, on the other. You need to find the most efficient system that still allows you enough control to do what your app needs to do. The other consideration is whether or not the PaaS system provides the services your app needs. Do you need message queueing, log aggregation, traffic analytics, etc.? It's good if there are multiple providers of the services you need in the ecosystem of the PaaS you intend to use.
In the wake of NSA revelations, security has become the number 1 issue.
Prior to that (and now second to security) is the degree to which it will integrate seamlessly with the rest of the enterprise platform, the speed and resilience of internetworking (in Africa this is huge), and the extent to which the platform is redundant, backed up and under my control for configuration purposes.
A free trial (without a credit card or a phone call) and clear pricing details are the important aspects that I look for while purchasing PaaS solutions.
TCO and ROI is always the only thing whenever you need an IT service and also sustainability as well.
The benefits that this service offers; to be able to upload and send files from the cloud without the complexity of accessing users.
The maturity of the API stack is important. The need for an API stack that takes into account private/hybrid cloud implementations is important (enterprise perspective).
Security, the potential for vendor lock-in, fit with IAAS infrastructure.
security with an intuitive interface
Support for multiple programing languages and frameworks, scalability and no lock in.
Availability of an easy to use Web interface to monitor and control the PaaS that should be able to run a Java WAR that runs locally without any change or constraint.