Application architecture considerations for cloud platforms

Sodhi, Balwinder; Prabhakar, T. V.

doi:10.1109/comsnets.2011.5716417

Cited by 6 publications

(9 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Similar research questions were found in works created by Sodhi et al (2011), Toffetti et al (2016), Kratzke and Quint (2017). However, they address different aspects of cloud-ready software development.…”

Section: Introductionmentioning

confidence: 58%

“…"Cloud-ready" is mentioned by Brown and Capern (2014) from IBM, Kavis (2014), andWeinman (2016). "Cloud-aware" term is met in Open Datacenter Alliance report (Casper et al (2014)) and Sodhi et al (2011). Andrikopoulos et al (2012) define cloud-native applications as ".…”

Section: Study Selectionmentioning

confidence: 99%

“…However there were multiple articles that were discussing architectural approaches for development of cloud-ready applications (Sodhi et al (2011)), principles (Andrikopoulos et al (2012)), patterns (Wilder (2012), Fehling et al (2011, 2014). Later works in this area were more related to conventional application migration to the cloud (Andrikopoulos et al (2013)) or development methods or frameworks (Inzinger et al (2014), Ardagna et al (2012)).…”

Section: [Rq3] What Architectures Are Currently Used For Cloud-ready mentioning

confidence: 99%

“…However, they address different aspects of cloud-ready software development. Sodhi et al (2011) discuss their proposed design approaches: cloud-aware and cloud-agnostic. These designs are used for development of application that will run on the cloud.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Systematic Literature Review of the Cloud-ready Software Architecture

Pozdniakova¹,

Mažeika²

2017

BJMC

View full text Add to dashboard Cite

Abstract. Many companies are adopting cloud for hosting applications delivered as a service over the Internet. An application service delivered in this way is referred as Software as a Service (SaaS). The SaaS providers get benefits from getting cloud resources provisioned on-demand and through pay-as-you-go billing models. These capabilities enable faster application development and deployment with lower upfront investment into infrastructure. To benefit the most from the cloud, software architecture must be designed with consideration that software will run on the cloud. However, a legacy application is often developed by using monolithic architecture approach and might not get all advantages provided by a cloud computing. A growing monolithic application gets less flexible in development, has longer provisioning time, slows down the speed of innovation and lowers economy of scale. As result of such problems, not only commercial companies, but also the various academic researchers aim to design software as a "cloud-native" application. This kind of software has specific non-functional requirements that define scalability, reliability, fault tolerance and other cloud-specific requirements. This systematic literature review is based on the case studies, published articles and other literature related to the cloud-native or cloud-ready applications. It generalizes common traits of non-functional requirements defined in analyzed resources. Also, it walks through architectural styles of the applications running on a cloud and presents recently developed architectures that are used for large-scale software services delivered on a cloud.

show abstract

Section: Introductionmentioning

confidence: 58%

Section: Study Selectionmentioning

confidence: 99%

Section: [Rq3] What Architectures Are Currently Used For Cloud-ready mentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Systematic Literature Review of the Cloud-ready Software Architecture

Pozdniakova¹,

Mažeika²

2017

BJMC

View full text Add to dashboard Cite

show abstract

“…As a result, the TSPACE SRA needs to incorporate architecture quality requirements of cloud-enables services based system such as scalability [9], multi-tenancy [10] and dynamic provisioning [11]. The activities that are performed at this stage aim to identify important quality characteristics with reference to the domain in which the TSPACE is to be used.…”

Section: Requirements Identification and Classificationmentioning

confidence: 99%

A Process Framework for Designing Software Reference Architectures for Providing Tools as a Service

Chauhan

Babar

Probst

2016

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Design comparison of traditional application and SaaS

Vidhyalakshmi

Kumar

2014

2014 International Conference on Computing for Sustainable Global Development (INDIACom)

View full text Add to dashboard Cite

Software as a Service (SaaS) is an on-demand software delivery model, where the software and its related data are placed at remote location and are accessed as a web based service using a thin client such as web browser over the Internet. The salient features of SaaS includes low startup cost, easy provisioning at the time of need, shorter release cycle, easy maintenance, cost saving on maintenance and upgradation, multi tenant architecture, etc. The advantages and the working pattern surely make it as a best option for Small and Medium Business Enterprises, when compared to traditional web applications. However the consideration of wide consumer base with different requirements specification for a single application leads to the complexity of SaaS design. The SaaS applications are based on protocols such as HTTP, SOAP and architecture design concept such as REST. Many development models have been used for SaaS design however most of the models have very little focus on the reliability. A perspective comparison has been presented in the paper work for the traditional applications and the SaaS applications. A number of desired characteristics have been outlined to increase the configurability, portability and reliability of the SaaS applications designs.

show abstract

Application architecture considerations for cloud platforms

Cited by 6 publications

References 3 publications

Systematic Literature Review of the Cloud-ready Software Architecture

Systematic Literature Review of the Cloud-ready Software Architecture

A Process Framework for Designing Software Reference Architectures for Providing Tools as a Service

Design comparison of traditional application and SaaS

Contact Info

Product

Resources

About