ClouNS - a Cloud-Native Application Reference Model for Enterprise Architects

Kratzke, Nane; Peinl, René

doi:10.1109/edocw.2016.7584353

Cited by 36 publications

(43 citation statements)

References 20 publications

(27 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Cloud-native definition provided in Kratzke and Peinl (2016) is more in alignment with current industry trends, like microservices and containers, which will be discussed in Subsection 3.3. Definitions provided in Andrikopoulos et al (2012), Toffetti et al (2016) and (2012) are more universal and technology agnostic.…”

Section: Study Selectionmentioning

confidence: 99%

“…Kratzke and Peinl (2016) in their cloud-native application reference model for enterprise architects, called ClouNS, raise an importance of vendor lock-in avoidance in cloud-ready application design. A systematic mapping study prepared by Kratzke and Qiuin (2017) provides a cloud-native application principles, like need of automation platforms, software defined infrastructure, migration and interoperability between the clouds.…”

Section: Study Selectionmentioning

confidence: 99%

“…Here are just few examples of our findings. Andrikopoulos et al (2012), Toffetti et al (2016), Wilder (2012), Kratzke and Peinl (2016), Kratzke and Quint (2017) are using "cloud-native" term in their works and each of them provides a definition for it. "Cloud-ready" is mentioned by Brown and Capern (2014) from IBM, Kavis (2014), andWeinman (2016).…”

Section: Study Selectionmentioning

confidence: 99%

“…Due to lack of common definition in academic literature, Kratzke and Peinl (2016) aim to define cloud-native application more explicitly: "A cloud-native application is a distributed, elastic and horizontal scalable system composed of (micro)services which isolates state in a minimum of statefull components. The application and each selfcontained deployment unit of that application is designed according to cloud-focused design patterns and operated on a self-service elastic platform".…”

Section: Study Selectionmentioning

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: Study Selectionmentioning

confidence: 99%

Section: Study Selectionmentioning

confidence: 99%

Section: Study Selectionmentioning

confidence: 99%

Section: Study Selectionmentioning

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

“…We provide a short review of cloud-native designs over the last 10 years in Section II, to get a better understanding of the trends in current cloud engineering. One noteworthy consideration is the vendor lock-in dilemma [1], [2]. Once a cloud application is deployed to a cloud infrastructure it is often inherently bound to that (conceptually centralized) infrastructure [3].…”

Section: Introductionmentioning

confidence: 99%

Towards Distributed Clouds: A Review About the Evolution of Centralized Cloud Computing, Distributed Ledger Technologies, and A Foresight on Unifying Opportunities and Security Implications

Westerlund¹,

Kratzke²

2018

2018 International Conference on High Performance Computing &Amp; Simulation (HPCS)

Self Cite

View full text Add to dashboard Cite

This review focuses on the evolution of cloud computing and distributed ledger technologies (blockchains) over the last decade. Cloud computing relies mainly on a conceptually centralized service provisioning model, while blockchain technologies originate from a peer-to-peer and a completely distributed approach. Still, noteworthy commonalities between both approaches are often overlooked by researchers. Therefore, to the best of the authors knowledge, this paper reviews both domains in parallel for the first time. We conclude that both approaches have advantages and disadvantages. The advantages of centralized service provisioning approaches are often the disadvantages of distributed ledger approaches and vice versa. It is obviously an interesting question whether both approaches could be combined in a way that the advantages can be added while the disadvantages could be avoided. We derive a software stack that could build the foundation unifying the best of these two worlds and that would avoid existing shortcomings like vendor lock-in, some security problems, and inherent platform dependencies.

show abstract