Choosing a platform as a service for software as a service provider
Kreivi, Antti (2014-04-24)
Kreivi, Antti
A. Kreivi
24.04.2014
© 2014 Antti Kreivi. Tämä Kohde on tekijänoikeuden ja/tai lähioikeuksien suojaama. Voit käyttää Kohdetta käyttöösi sovellettavan tekijänoikeutta ja lähioikeuksia koskevan lainsäädännön sallimilla tavoilla. Muunlaista käyttöä varten tarvitset oikeudenhaltijoiden luvan.
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:oulu-201404291316
https://urn.fi/URN:NBN:fi:oulu-201404291316
Tiivistelmä
Cloud computing is still very sparsely researched, especially concerning platform as a service(PaaS) deployment model. PaaS model is still a very new in cloud computing and often confused with more familiar IaaS and SaaS models. First the basic concepts of cloud computing such as essential characters, deployment models and service models are presented and everything in cloud computing lean on these main concepts.
The main objectives in this thesis are, to find out why PaaS is better alternative than building an own platform over a selected infrastructure, and to justify, why the selected PaaS is the most suitable for a cloud software project. PaaS has many advantages and concerns that must be sort out before a decision of deploying one can be made. With PaaS, developers do not need to know much about underlying cloud infrastructure and the infrastructure services are usually completely hidden, instead they can focus more on the development. PaaS platforms bring also a lot of cost reductions from reduced hardware needs, staff and more predictable expenditure. The biggest challenges in PaaS are the security and privacy concerns, and possible vendor lock-in risks.
The four PaaS alternatives which are measured are Amazon Web Services with Beanstalks, Google App Engine, Heroku and Cloud Foundry. These are selected from number of alternatives together with the contractor. These four were among the most well-known PaaS providers and they were the most suitable with the contractor’s project and with the criteria. To measure these, five justified criteria, which are derived from the literature, are defined. Measurable factors are derived from scalability, service agreements and vendor lock-in, security, framework and supported languages and pricing models.
Choosing-by-advantage(CBA) decision making method is used to find out the best alternative. CBA is made for fast and sound decision making and it is based on the importance of advantages. The factors from the criteria are derived in away that they should uncover the advantages of each PaaS alternative. Disadvantages are also found out and listed to strengthen the decision further. With the help of the justified criteria and the CBA analysis, the goal is to support and justify the PaaS decision, which will be made.
The main objectives in this thesis are, to find out why PaaS is better alternative than building an own platform over a selected infrastructure, and to justify, why the selected PaaS is the most suitable for a cloud software project. PaaS has many advantages and concerns that must be sort out before a decision of deploying one can be made. With PaaS, developers do not need to know much about underlying cloud infrastructure and the infrastructure services are usually completely hidden, instead they can focus more on the development. PaaS platforms bring also a lot of cost reductions from reduced hardware needs, staff and more predictable expenditure. The biggest challenges in PaaS are the security and privacy concerns, and possible vendor lock-in risks.
The four PaaS alternatives which are measured are Amazon Web Services with Beanstalks, Google App Engine, Heroku and Cloud Foundry. These are selected from number of alternatives together with the contractor. These four were among the most well-known PaaS providers and they were the most suitable with the contractor’s project and with the criteria. To measure these, five justified criteria, which are derived from the literature, are defined. Measurable factors are derived from scalability, service agreements and vendor lock-in, security, framework and supported languages and pricing models.
Choosing-by-advantage(CBA) decision making method is used to find out the best alternative. CBA is made for fast and sound decision making and it is based on the importance of advantages. The factors from the criteria are derived in away that they should uncover the advantages of each PaaS alternative. Disadvantages are also found out and listed to strengthen the decision further. With the help of the justified criteria and the CBA analysis, the goal is to support and justify the PaaS decision, which will be made.
Kokoelmat
- Avoin saatavuus [29905]