Container and Microservice Driven Design for Cloud Infrastructure DevOps

Kang, Hui; Le, Michael; Shu, Tao

doi:10.1109/ic2e.2016.26

Cited by 157 publications

(70 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…These specifications generate container images in the build stage, which are later instantiated in the target environment. Docker has been used not only for deploying applications but also for deploying the underlying infrastructure [26].…”

Section: Tools For Deployment Automationmentioning

confidence: 99%

See 1 more Smart Citation

A Survey of DevOps Concepts and Challenges

Leite¹,

Rocha

Kon³

et al. 2019

ACM Comput. Surv.

316

183

View full text Add to dashboard Cite

DevOps is a collaborative and multidisciplinary organizational effort to automate continuous delivery of new software updates while guaranteeing their correctness and reliability. The present survey investigates and discusses DevOps challenges from the perspective of engineers, managers, and researchers. We review the literature and develop a DevOps conceptual map, correlating the DevOps automation tools with these concepts. We then discuss their practical implications for engineers, managers, and researchers. Finally, we critically explore some of the most relevant DevOps challenges reported by the literature.

show abstract

Section: Tools For Deployment Automationmentioning

confidence: 99%

“…On the other hand, in containerization the whole containerized environment is generated in the build, so the environment is destroyed and rebuilt at each new software version. When compared to the Chef strategy, Docker yields faster and more reliable deployment [26], but at the expense of bigger builds.…”

Section: Tools For Deployment Automationmentioning

confidence: 99%

A Survey of DevOps Concepts and Challenges

Leite¹,

Rocha

Kon³

et al. 2019

ACM Comput. Surv.

316

183

View full text Add to dashboard Cite

show abstract

“…However, some attributes scored fewer occurrences which implied lack of consideration. These attributes were basically security ID [15,18,23,32,33], load balancing ID [1,20] and organizational alignment ID [13,15]. In addition to the results of research questions 2 and 3 above, we decided to investigate a possible relationship between quality attributes in the literature and model views presented.…”

Section: Quality Attributes Related To Microservices In Literature (Rmentioning

confidence: 99%

A Systematic Mapping Study in Microservice Architecture

Alshuqayran

Alí

Evans

2016

2016 IEEE 9th International Conference on Service-Oriented Computing and Applications (SOCA)

291

146

View full text Add to dashboard Cite

Abstract-The accelerating progress of network speed, reliability and security creates an increasing demand to move software and services from being stored and processed locally on users' machines to being managed by third parties that are accessible through the network. This has created the need to develop new software development methods and software architectural styles that meet these new demands. One such example in software architectural design is the recent emergence of the microservices architecture to address the maintenance and scalability demands of online service providers. As microservice architecture is a new research area, the need for a systematic mapping study is crucial in order to summarise the progress so far and identify the gaps and requirements for future studies. In this paper we present a systematic mapping study of microservices architectures and their implementation. Our study focuses on identifying architectural challenges, the architectural diagrams/views and quality attributes related to microsevice systems.

show abstract

“…MSA defines each service to be totally independent [4] with its own database. When MSA is defined with completely isolated No-SQL databases [6], and when the business transactions span across multiple services, the state changes in one database entity are not visible to state changes in the other.…”

Section: Introductionmentioning

confidence: 99%

Comparison of Event Choreography and Orchestration Techniques in Microservice Architecture

Rudrabhatla¹

2018

ijacsa

View full text Add to dashboard Cite

Abstract-MicroserviceArchitecture (MSA) is an architectural design pattern which was introduced to solve the challenges involved in achieving the horizontal scalability, high availability, modularity and infrastructure agility for the traditional monolithic applications. Though MSA comes with a large set of benefits, it is challenging to design isolated services using independent Database per Service pattern. We observed that with each micro service having its own database, when transactions span across multiple services, it becomes challenging to ensure data consistency across databases, particularly in case of roll backs. In case of monolithic applications using RDBMS databases, these distributed transactions and roll backs can be handled efficiently using 2 phase commit techniques. These techniques cannot be applied for isolated No-SQL databases in micro services. This research paper aims to address three things: 1) elucidate the challenges with distributed transactions and rollbacks in isolated No-SQL databases with dependent collections in MSA, 2) examine the application of event choreography and orchestration techniques for the Saga pattern implementation, and 3) present the fact-based recommendations on the saga pattern implementations for the use cases.

show abstract

Container and Microservice Driven Design for Cloud Infrastructure DevOps

Cited by 157 publications

References 3 publications

A Survey of DevOps Concepts and Challenges

A Survey of DevOps Concepts and Challenges

A Systematic Mapping Study in Microservice Architecture

Comparison of Event Choreography and Orchestration Techniques in Microservice Architecture

Contact Info

Product

Resources

About