Service provider DevOps for large scale modern network services

Kim, Juhoon; Meiroşu, Cătălin; Papafili, Ioanna; Steinert, Rebecca; Sharma, Sachin; Westphal, Fritz-Joachim; Kind, Mario; Shukla, Apoorv; Németh, Felicián; Manzalini, Antonio

doi:10.1109/inm.2015.7140502

Cited by 19 publications

(6 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The larger number of challenges, eg, C01, C02, C03, C04, C05, C06, C08, C09, C13, C14, C17, C18, C19, C22, C24, C25, C27, C28, C29, C30, C31, C32, C33, C34, C35, C36, C38, and 41 are about DevOps adoption. ()…”

Section: Resultsmentioning

confidence: 99%

Towards a benefits dependency network for DevOps based on a systematic literature review

Jabbari

Ali

Petersen

et al. 2018

J Software Evolu Process

View full text Add to dashboard Cite

DevOps as a new way of thinking for software development and operations has received much attention in the industry, while it has not been thoroughly investigated in academia yet. The objective of this study is to characterize DevOps by exploring its central components in terms of principles, practices and their relations to the principles, challenges of DevOps adoption, and benefits reported in the peer-reviewed literature. As a key objective, we also aim to realize the relations between DevOps practices and benefits in a systematic manner. A systematic literature review was conducted. Also, we used the concept of benefits dependency network to synthesize the findings, in particular, to specify dependencies between DevOps practices and link the practices to benefits. We found that in many cases, DevOps characteristics, ie, principles, practices, benefits, and challenges, were not sufficiently defined in detail in the peer-reviewed literature.In addition, only a few empirical studies are available, which can be attributed to the nascency of DevOps research. Also, an initial version of the DevOps benefits dependency network has been derived. The definition of DevOps principles and practices should be emphasized given the novelty of the concept. Further empirical studies are needed to improve the benefits dependency network presented in this study. KEYWORDSbenefits and values, challenges, development and operations, DevOps, principles and practices, systematic literature review

show abstract

Section: Resultsmentioning

confidence: 99%

Towards a benefits dependency network for DevOps based on a systematic literature review

Jabbari

Ali

Petersen

et al. 2018

J Software Evolu Process

View full text Add to dashboard Cite

show abstract

“…Microservice architecture has gained popularity in recent time across all the software domains as a new and emerging software architecture. Microservice architecture is thought to be one of the major driver in enabling cloud-native devops [13], [14]. The existing software architectures like SOA (Service Oriented Architecture) is being compared with the microservices architecture to create a case for the large scale adoption [11].…”

Section: Related Workmentioning

confidence: 99%

On Monolithic and Microservice Deployment of Network Functions

Sharma

Uniyal

Tola

et al. 2019

2019 IEEE Conference on Network Softwarization (NetSoft)

Self Cite

View full text Add to dashboard Cite

Network Function Virtualization (NFV) has recently attracted telecom operators to migrate network functionalities from expensive bespoke hardware systems to virtualized IT infrastructures where they are deployed as software components. Scalability, up-gradation, fault tolerance and simplified testing are important challenges in the field of NFV. In order to overcome these challenges, there is significant interest from research communities to scale or decompose network functions using the monolithic and microservice approach. In this paper, we compare the performance of both approaches using an analytic model and implementing test-bed experiments. In addition, we calculate the number of instances of monoliths or microservices in which a network function could be scaled or decomposed in order to get the maximum or required performance. Single and multiple CPU core scenarios are considered. Experimentation is performed by using an open source network function, SNORT and running monoliths and microservices of SNORT as Docker containers on bare metal machines. The experimental results compare the performance of monolith and microservice approaches and are used to estimate the validity of the analytic model. The results also show the effectiveness of our approach in finding the number of instances (monoliths or microservices) required to maximize performance.

show abstract

“…Bruneo et al [12] used DevOps concept to develop an adaptive cloud management platform. Kim et al [13] even discussed the DevOps requirements specific to the modern network service creations, and proposed an extended DevOps concept.…”

Section: Innovative Achievementmentioning

confidence: 99%

Exploring DevOps for Data Analytical System with Essential Demands Elicitation

Zheng

Liu

Lin³

2016

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

Abstract-DevOps is an emerging concept and methodology for bridging the gap in the process of software development. At present, applying DevOps to data analytical system (DAS) is increasingly embraced. But the characteristics of this system, such as data protection, always leads to a series of constrains. It's a bit difficult to conduct DevOps on data analytical system. Moreover, there are no DevOps solutions for reference. Therefore, exploring DevOps for data analytical system is valuable.In this paper, we illustrate DevOps demands of data analytical system from different perspectives, and constantly emphasize the importance of automation toolchain. Based on them, a process model for DAS DevOps (D 2 Ops) is proposed to clarify participants activities. In order to improve the efficiency, we attempt to integrate the automation toolchain. With the consideration of stability, six generic process components are designed to support this model. They can be the selection criteria for specific automation tools. We also present a reference facility based on these generic process components, and illustrate its implementation combing with a practical case.

show abstract

Service provider DevOps for large scale modern network services

Cited by 19 publications

References 4 publications

Towards a benefits dependency network for DevOps based on a systematic literature review

Towards a benefits dependency network for DevOps based on a systematic literature review

On Monolithic and Microservice Deployment of Network Functions

Exploring DevOps for Data Analytical System with Essential Demands Elicitation

Contact Info

Product

Resources

About