2021 International Conference on Nascent Technologies in Engineering (ICNTE 2021)

Blockchain based framework for Software

Development using DevOps
Sandip Bankar
Dr. Deven Shah
Department of Information Technology,
Department of Information Technology,
Thakur College of Engineering and Technology,
Thakur College of Engineering and Technology,
Mumbai, India
Mumbai, India
[email protected]
[email protected]
2021 4th Biennial International Conference on Nascent Technologies in Engineering (ICNTE) | 978-1-7281-9061-7/21/$31.00 ©2021 IEEE | DOI: 10.1109/ICNTE51185.2021.9487760

Abstract— The Varity and complexity of software development organization work standards, Agile methodology was found not
methods is getting increased from mid-1960, to accelerate enough [2]. DevOps is a new development technology which
product’s time to market it is more and more pervasive so it has emerged from Agile Methodology with collaboration
becomes crucial to ensure the quality, performance, and security between development and operations teams in every stage of
of software product in untrustworthy environment. DevOps
life cycle. DevOps is an IT culture, it consists of various
focuses on automation and inter departmental integration to
create an environment and culture that will increase software practices and the approaches that influence organizations in
development speed as there are frequent conflicts occurs between organizing teams, build systems and influence even the
development and operations. This paper focusses on architecture structure of the systems that you build [3]. It is software
that redefines the DevOps pipeline by positioning Blockchain development practice in which developers and operations
technology in this environment. It stores all project artifacts on stakeholders work together in DevOps life cycle stages from
decentralized and secure Blockchain environment so that it can development to production but most of the time, work is done
create trust between people with dishonest and stubbornness in a centralized environment where the service availability is
mindset that would make DevOps delivery to follow control not guaranteed also in the presence of malicious users.
requirements in technology and business environments of
different sizes. Separately, blockchain and DevOps provides At an application level, cloud frameworks are also
tangible and quantifiable value for just about any type of business. centralized. Henceforth, there is requirement for a decentralized
If they are used together, they can form a highly advanced business framework simultaneously not settling on security is also
solution that can revolutionize services, operations and important.
collaborations.
Blockchain, a Distributed Ledger technology which is
Keywords— DevOps, Blockchain, Hyperledger Fabric, shared between peers, acknowledged by consensus, is utilized
Interplanetary File System. to make business measures secure and transparent [4].
I. INTRODUCTION Consensus algorithms are characterized in the Blockchain smart
contracts [4], i.e., programs that naturally execute predefined
The software development industry is exceptionally activities when conditions in the framework are fulfilled. The
becoming complex, tremendous and dynamic day by day. permanent history of records kept up in the Distributed Ledger
Software development is an essential aspect of the business and characterizes information genuineness and security in the
is legitimately affected by some elements, including developing framework.
complexities, economic situations, changing innovation drifts
just as software development improvement challenges. In the accompanying sections of the paper, discussions on
the related work in the domain of Software Development
Organizations develop software projects are facing Models, DevOps and Blockchain shall be explored in Section
difficulties for making decision of picking the correct software II to comprehend the inadequacies of the current systems.
development method [1]. They originated from the first and section III on proposed framework will clarify the strategy
oldest SDLC model that is waterfall method, and their range utilized in the paper to address some of the research gaps.
grew significantly. The scope of SDLC models is dictated by Section IV on Implementation and results, the implementation
the wide range of product types-starting with the development gives a demonstration of the proposed solution, trailed by
of web applications to complex medical devices. The problem Section V, the paper concludes with future scope.
with ‘Agile methodology’ came into picture when things started
to get difficult for the organizations who took up client services. II. RELATED WORK
There was very less coordination between the teams from all Since the evolution of the project management era, within
levels, specifically teams those were responsible for developing the 1950’s, many software methodologies were evolved, most
the service (development team) and the teams responsible for appreciably Waterfall, PMBOK, PRINCE2 and Agile.
bringing the service into delivery phase/ production phase onto Waterfall methodology has two commonly reasons of failure: it
the customer’s hand (operations team). The operations team does not allow a dynamic changes and availability of the whole
was not on the same pace as the development team. So, for some

978-1-7281-9061-7/21/$31.00 ©2021 IEEE

Authorized licensed use limited to: Centro de Est. e Sistemas Avançados Recife (CESAR). Downloaded on April 01,2023 at 14:49:33 UTC from IEEE Xplore. Restrictions apply.
 2021 International Conference on Nascent Technologies in Engineering (ICNTE 2021)

system is possible only after finishing all stages. While acceptance and implementation in organizations that is
Waterfall methodology have become more and more criticized observed to be non-trivial because of essential changes in
due to their inflexibility, but some other methods are much technical, organizational and cultural components.
more efficient and also flexible, which emerged in new
Challenges in DevOps are high need of knowledge, Unclear
software development model, Agile methodology. After
responsibilities between development and operations,
finalizing the overall purpose of the project, the people work in
Difficulties in convincing senior control, Lack of common
a less demanding regulatory background and tails an
understanding [8].
incremental method, that specialize in delivering the software
components within given time, known as sprints. But it includes A Survey of DevOps Concepts and Challenges by Leonardo
some drawbacks, the main important of reason of failure that Leite et al. present survey which explores and debates, the
the end result doesn't meet the client requirements. Another DevOps challenges from the angle of engineers, managers, and
downside to the surpassing of exceeding time and budget, on researchers. Some challenges are diagnosed with examine of
account of the unpracticed group and, especially, to an over 200 papers,230 books, and 100 tools. They may be human
unpracticed manager. It has been resolved that the detachment association crosswise departments with automation and its
between software development improvement and operation miles made clear that the DevOps has irrevocably unclear the
tasks can cause deferred disclosure of mistakes and in like boundary among developers and operations [9].
manner, to move the deadline time of projects. Accordingly, it
Akond Ashfaque et al. have tried to integrate security by
has arisen another software culture, DevOps [5].
analysis of internet artifacts, providing security training to
DevOps indicates the culture which is combination of security teams [10].
software development and operations, with an emphasis on
A. Limitations of related work
departmental integration and automation. Recent work is
shifting from traditional software development methodology to Authors have tried to optimize software delivery process by
DevOps processes. DevOps came into existence due to certain applying different techniques, but lack of trust between
problems in the traditional way of handling development and development and operations teams exist, so it results into
operations teams. DevOps is mode of work, through the usage communication, collaboration gap. When problem occurs,
of a chain of tools for the growth the collaborations between people blame between teams to neglect responsibilities, as there
development teams and operations teams to reduce the conflicts are different software versions and dependencies with
among the two teams also it enhances the improvement heterogeneous environments.
efficiency and quality. In DevOps environment, detachment of responsibilities
DevOps isn't so far appropriately defined as method; IT become dividers which genuinely isolating teams, which in the
researchers are not influenced to use it for numerous reasons, long run increments in the quantity of errand of developments,
which include the deficiency of a standard definition and the deployment, testing and support resources, which slows the
main features, in order that each implementation is delivery of the product. To fasten the execution of DevOps in
accomplished in a custom designed way. DevOps uses the same an industry, it is need of an imaginative solution that will
standards as Agile technique, including additional operation proficiently and perfectly implement controls in software
and functionality of the projects [5]. development environment.
Versioning Strategy for DevOps Implementations [6], B. Continuous Monitoring and its drawbacks
covers the identity of project artifacts, version naming DevOps involves a lot of tools and processes that go within
conventions, versioning tools and traceability between artifacts an organization's pipeline. Monitoring of these tools play a
variations. Also, it is attempted to convey documentation major role in management of tools [5]. When an organization
artifacts and source code artifacts under version control. They automates their pipeline, namely implementing a Continuous
have used semantic versioning approach to split distinct Integration / Continuous Deployment (CI/CD) model for their
versions. software engineering process, they need to be also ready for the
Research study on Factors inhibiting the adoption of different problems that can occur at each stage of the pipeline.
DevOps in large enterprise identifies the five primary elements Generally, companies tend to use tools like Nagios or rely upon
cloud services for their deployment procedures but using a tool
deterring the acceptance of DevOps, particularly: loss of
also requires you to itself manage that tool since they are
strategic plan from senior management; lack of knowledge
licensed and versioned preciously. Companies cannot afford to
around DevOps; chance of disintermediation of roles; struggle
spend time looking after the tools. Most software organizations
to change; and silo mentality. Silos are departments employee
that have a tendency to be characterized by way of a failure in lack the idea of monitoring their pipeline from start to finish in
communication, synchronization and collaboration. It is vital to an environment of multiple microservices, where their product
is ready or stuck somewhere in the pipeline. Monitoring
comprise control feedback, check and track progress against the
solutions that companies are trying to adopt can become quite
strategic targets [7].
complex when they have numerous microservices to look after.
Lucy Ellen et al. have carried out review on five different
businesses to find out DevOps effects and challenges, DevOps

Authorized licensed use limited to: Centro de Est. e Sistemas Avançados Recife (CESAR). Downloaded on April 01,2023 at 14:49:33 UTC from IEEE Xplore. Restrictions apply.
 2021 International Conference on Nascent Technologies in Engineering (ICNTE 2021)

So, to improve security practices, it is necessary to create an contract (chaincode) are fulfilled and consensus algorithm isn't
environment whereby an unscheduled or unauthorized change violated, at that point only the block is admitted to the chain.
will be identified and corrective action will be taken. The aim This spares a ton of operational and equipment cost, without
is to design a culture and environment that will increase settling on throughput, which is particularly significant for this
development and delivery speed through automation and to application [14].
reduce costs.
III. PROPOSED FRAMEWORK
Today’s organizations aggressively trying to adopt DevOps,
but can we use blockchain and accelerate DevOps
implementation for large enterprise? In software Source Code
(code repositories), artifacts (CI/CD, automation), files
(configuration, definition, description, documentation),
container (images, layer) are used across all the departments,
and are barely ever available at a single location. Through this
paper, we present, how this integral inefficiency can be
restricted by bringing all the stakeholders for all the documents
on a single decentralized network, so transparency can be
established. The goal of this work is to support all of DevOps
processes, without touching them and without disrupting the
automation in any way. This solitary platform preserves a track
record of every change to any file in software development
process on secure tamperproof blockchain network.
C. Architecture Overview
Conceptual solution using permissioned blockchain
Architecture which is shown in Figure 1, shows the overall
architecture which covers the different participants, inclusion
Fig. 1. Architecture for DevOps with Blockchain
of the Distributed Database (IPFS) and Permissioned
Blockchain Network (Hyperledger Fabric). It shows
decentralized solution with new intermediary that would Hyperledger Fabric addresses performance scalability and
sequentialize delivery, auditability and immutability. This privacy issues, typically found in a permissioned type of
choice of underlying blockchain infrastructure is independent blockchain. So, for the reasons talked above, Hyperledger
of the approach, implemented processes or on user experience. Fabric was chosen for the usage of the proposed
implementation so we can have industry individuals on
D. Role of DevOps permissioned blockchain stage. As shown in figure 2, manager
This proposed system consists of a deployment pipeline that or director or any stakeholder through application SDK sends a
permits parallel monitoring service and storage of software request to the Endorsing peer, which runs the chaincode to
development artifacts in a decentralized database. This work check whether it fulfils the business logic to track updates to
focuses on preventing the problems of having a centralized records and putting away them on blockchain. At this point it
architecture in the pipeline. Furthermore, keeping the sends the first transaction with read and write response set, back
blockchain channels locally available will not disrupt the with a sign, for the customer to check if incorrect derivation was
development team from committing their code and checking drawn while checking rules of chaincode.
whether it fits with all the other modules coming from other
● Fig. 2. Transactions flow in the proposed system [13]
teams built into one executable application.
E. Role of Blockchain
This work enables transparency throughout the pipeline
with the use of permissioned blockchain. Compliance
specialists are able to fetch a summarized report of all the
relevant data that can be flexibly added. Continuous Monitoring
is also enabled throughout the pipeline as the underlying
blockchain is storing all the transactions such as data entering /
passed to a tool at each stage in pipeline and similarly recording
the output from each tool.
Thereby ensuring that each transaction that occurred can be
traced back to know relevant details about a certain stage of the This permits the SDK to send the transaction to the
pipeline Business logics and conditions expressed in the smart blockchain. Orderer joins these transactions into blocks, for all
the channels in the network. Arranged blocks are received by

Authorized licensed use limited to: Centro de Est. e Sistemas Avançados Recife (CESAR). Downloaded on April 01,2023 at 14:49:33 UTC from IEEE Xplore. Restrictions apply.
 2021 International Conference on Nascent Technologies in Engineering (ICNTE 2021)

the Committing and Endorsing Peers, they will approve every of document created and can be stored in Blockchain. These
transaction and commit to blockchain [4]. documents can be stored on blockchain so that their
immutability can be achieved and all updates to them can be
TABLE I. ROLE OF SYSTEM ENTITIES IN A TABULAR FORM
tracked to create trust among stakeholders of the DevOps
Node in Network Function of Node methodology.
Client SDK: Admin/Director It sends request to Endorsing peer,
submits new transaction waits for approval
Endorsing Peers: Developers It runs smart contracts to see
validity of SDK’s request
Ordering Nodes: Peers/Managers Collects transaction into blocks
and distributes to other peers
Committing Peers: stakeholders Commits block to the blockchain

F. Role of IPFS
The backend file store, IPFS (InterPlanetory File System)
file store allows us to store files on IPFS nodes set in a network
or in a cluster of nodes on the network and provides a way to
access these files rapidly without huge latency that was caused ● Fig. 4. DevOps phases with type of document on Blockchain.
due to dependency on a faraway server that hosts the file. So
even when a node or peer who is situated physically next to us For comfort of demonstration, the solution is implemented
has the file you desire, the network fetches the file contents on Hyperledger Composer and fabric as permissioned
from that node and does not rely on the central server. Nodes blockchain. Hyperledger Fabric needs to Chaincode to be
communicate with each other and they are able to store the files written in Go or NodeJS. As shown in Figure 5, in this system
of each other [15]. They only store the files that are requested Front end is developed using ReactJS, for backend and
by the nodes themselves. blockchain implementations NodeJS is used. In blockchain, file
versions are stored according to their update history. Every
malicious attempt is been recorded in the Blockchain’s
transaction history. Anytime, the admin can check the
malicious or invalidated attempts in the system and thus, can
terminate an employee from the system or project.
● Fig. 5. Three-layer proposed architecture with implementation

Fig. 3. IPFS content-based addressing

Figure 3 shows the way this work and stores hashes of

different directories in a JSON file. It allows us to keep track of
the different versions irrespective of whether it’s a single file or
a batch of files since any uploaded file is stored in a directory
named ‘DocumentsDir’. The ‘dirHash’ JSON array stores
different versions of the directory hash as and when the files
within the directory are modified or new files are added. Proposed methodology implementation is divided into two
phases Continuous Development, Continuous Operations.
IV. IMPLEMENTATION AND RESULTS ● Continuous DevelopmentProject Manager and client
The proposed system is implemented by introducing interaction: Initially when the clients come with their
blockchain for transparency in the realm of software project to the organization in order to get their work
development, such that all the transactions or updates to done, he/she will communicate with the project manager
different files made are accessible to every stakeholder and their via the client interface which will keep the track of their
history is recorded. By using Blockchain into this solution, it is communication so that no party can repudiate on what
confirmed that each modification occurs in DevOps they have agreed on. Also, the interface serves as a
environment can be logged into the blockchain, then all the platform to share the project’s status with the client as
stakeholders can see if any changes that have made to the they are the most important stakeholders. The interface
record. Following Figure 4 shows DevOps phases with the type

Authorized licensed use limited to: Centro de Est. e Sistemas Avançados Recife (CESAR). Downloaded on April 01,2023 at 14:49:33 UTC from IEEE Xplore. Restrictions apply.
 2021 International Conference on Nascent Technologies in Engineering (ICNTE 2021)

has the functionality to share documents or any other

kind of attachment with each other.
● Project Initiation: The employee of the organization will
create a project with a unique project id. At this stage the
employee credentials that is their card is checked for the
access. If the card is tampered, then Blockchain will
raise an error and would not allow the user. If the user is
legit then a project metadata is made into the
Blockchain’s state database. Next, a project’s git repo is
made into the IPFS database. Following this, the project
owner can add collaborators to its project repo. If the
project owner keeps the project private then only
collaborators can perform CRUD operations on it. For Fig. 6. Process flow of creating user
the others (non-collaborators of the repo in the ● Update File: If any stakeholders want to update any file
organization), the project will not be visible. then he can get that file from blockchain based version
● Blockchain to IPFS Communication: For any operation control
on a project, the user is first authenticated and authorized
H. Integration and Deployment
by the blockchain and if the user is legit then the request
is passed to the IPFS server with an authorization token. Continuous integration (CI) is an event which occurs when
After the successful transaction on IPFS, it generates a one will be passing their production ready code to software
new hash of the project which is then provided to the which is given certain steps and procedures to perform when
receiving the trigger to compile and produce an executable
authentication server in order to update the project hash
version of the project by integrating all the modules collectively
in the blockchain’s state database.
puting together in the Code Repository. The utilization of a git
● Enabling all Git operations: The git operations are repository acts as a trigger for the build server to compile,
executed at the IPFS server, where after each operation execute and take a look at the code changes. If code changes
the repo is been updated at all the clusters. Thus, several cause the automatic take a look at cases to fail, associate alarm
updated copies of repo are maintained. This system
supports all the git features like add, commit,
maintaining commit history, merge, etc. Moreover,
merge conflicts can be resolved using the web UI or the
Cli at ease.
● Developing Custom Cli: A custom cli is made in order
to perform the git operations on remote repo. Generally,
the official git cli can’t be integrated with the
blockchain’s authentication mechanism. So, this custom
cli prompts the user first to authenticate with the
blockchain’s authentication server after which the
operations can be made at the remote repo.
are raised to tell the developers that their amendment was a
G. Functions supported in development phase failure.
Admin creates user in which user gets identity materials
● Fig. 7. Specific Project Page to create file
like key pairs and certificates. Using certificate or card, user
can login to the system. Process of creating user in shown
Continuous Delivery / Deployment (CD) is a process
in Figure 6.
wherein one will be able to completely automate the procedures
● Create Project: Initially project will be created by
of deployment until just before deploying to production or
administrator or manager. automate all the processes entirely till the production server.
● Add Member: Once project is created then manager
can add collaborators to it. Only team members will be Jenkins: Jenkins is an Continuous Integration tool that has
able to work on the files in that specific project. the ability to utilize preinstalled (or user installed) plugins
● Create File: The blockchain network uses Hyperledger and/or make use of a script file that defines all the commands
Composer, linked to the front-end ReactJS using and procedures, it has to perform in order to carry out the
REST-API. Files or artifacts can be created by using process of building a project and making sure every time all the
corresponding tabs on front end. The screenshot to testing and integration building has happened appropriately.
create file is shown in figure 7. I. Advantages of proposed work
● All documents history can be traced and province of any
change is easily achieved.

Authorized licensed use limited to: Centro de Est. e Sistemas Avançados Recife (CESAR). Downloaded on April 01,2023 at 14:49:33 UTC from IEEE Xplore. Restrictions apply.
 2021 International Conference on Nascent Technologies in Engineering (ICNTE 2021)

● All heterogenous, remote stakeholders can be brought [7] Morgan B. Kamuto,Josef J. Langerman, “Factors inhibiting the adoption
on single platform. of DevOps in large organisations: South African context”, 978-1-5090-
3704-9/17/$31.00 2017 IEEE
● All documents are stored on blockchain in tamperproof
[8] Lucy Ellen Lwakatare, TerhiKilamo, TeemuKarvonen, Tanja Sauvola,
way.
Ville Heikkilä,” DevOps in practice: A multiple case study of five
● It will try to avoid blame game situation occurrence in companies”,Elsevier Information and Software Technology 114 (2019)
development process. 217–230
● All latest updates can be easily available to each [9] Leonardo Leite, Carla Rocha, Fabio Kon, DejanMilojicic, Paulo
stakeholder so eventually fasten software delivery Meirelles,” A Survey of DevOps Concepts and Challenges, 2019
process. Association for Computing Machinery.0360-0300/2019/11-ART127
$15.00
V. CONCLUSION AND FUTURE SCOPE [10] Akond Ashfaque Ur Rahman, Laurie Williams,“Software Security in
DevOps: Synthesizing Practitioners’ Perceptions and Practices”
To overcome the issues faced by the present software
[11] Kimberly Connors, Abhishek Sinha, Petar Nikolic, Ivica Popovic, Ron
development lifecycle like DevOps, principles consolidated by Stokes,” Blockchain in DevOps Implementing transparent continuous
Hyperledger Fabric blockchain helps system very well. The delivery”, ey.com/ca
imbuement of Blockchain into the DevOps framework makes [12] VERITIS,“DEVOPS A Successful Path To Continuous Integration And
auditable, tamper-proof, traceable, with slight to no space for Continuous Delivery”, 2019 Veritis Group Inc
fraudulence. This framework unites artifacts needed for [13] Himani Mukne, Prathamesh Pai, Saish Raut, Dayanand Ambawade,
software development and stores on blockchain platform with “Land Record Mangement using Hyperledger Fabric and IPFS”, IEEE
45670 10th ICCCNT 2019 July 6-8, 2019, IIT Kanpur, India
single, decentralized, peer-to-peer network, it provides access
[14] Arxiv.org. Hyperledger Fabric: A Distributed Operating System for
to, all the stakeholders which are involved in the software Permisioned Blockchain https://arxiv.org/pdf/1801.10228
development. It creates a uniform platform for DevOps from [15] N. Nizamuddina, K. Salaha, M. Ajmal Azadb , J. Arshadc , M.H.
continuous development to continuous deployment by Rehman,” Decentralized document version control using ethereum
replicating it over Blockchain network. Blockchain makes it blockchain and IPFS
each file access, modification transparent, authenticated and “,https://doi.org/10.1016/j.compeleceng.2019.03.014 0045-7906/© 2019
Elsevier
secure due to the smart contract and hence makes them secure
[16] Sebastian Henningsen, Sebastian Rust ,Björn Scheuermann, Martin
against inside as well as outside malicious users and attackers. Florian, “Mapping the Interplanetary Filesystem”
The use of the proposed framework in industries of fast [17] Emmanuel Nyaletey , Reza M. Parizi , Qi Zhang ,“BlockIPFS -
software application development, deployment, an all-around Blockchain-enabled Interplanetary File System for Forensic and Trusted
Data Traceability” 2019 IEEE International Conference on Blockchain
planned, risk based DevOps delivery actualized then it will (Blockchain), 978-1-7281-4693-5/19/$31.00 2019 IEEE
engage consistence, improve controls, smooth out and upgrade [18] Parth thakkar, senthil Nathan,balaji viswanathan ,” Performance
key deliveries of products. Thus, it will build an organization's Benchmarking and Optimizing Hyperledger Fabric Blockchain
profitability and efficiency. This idea can also be strengthened Platform”, 2375-0227/18/$31.00 2018 IEEE DOI
by making it interoperable with combining different blockchain 10.1109/MASCOTS.2018.00034
platform networks. [19] Mahdi H. Miraz and Maaruf Ali, “Blockchain Enabled Smart Contract
Based Aplications: Deficiencies with the Software Development Life
VI. REFERENCES Cycle Models”, Baltica Journal, Vol. 33, 20th January 2020, ISSN: 0067-
3064, pp. 101-116
[1] Gaurav Kumar,Pradeep Kumar Bhatia, ”Comparative Analysis of [20] Simone Porru, Andrea Pinna, Michele Marchesi, Roberto Tonelli,”
Software Engineering Models from Traditional to Modern Blockchain-oriented Software Engineering: Challenges and New
Methodologies”, 978-1-4799-4910-6/14 $31.00 © 2014 IEEE Directions”, : https://www.researchgate.net/publication/313844963
[2] Sheetal Sharma,Darothi Sarkar,Divya Gupta, ”Agile Processes and [21] Kimberly Connors, Abhishek Sinha, Petar Nikolic, Ivica Popovic, Ron
Methodologies: A Conceptual Study “ , International Journal on Stokes,” Blockchain in DevOps Implementing transparent continuous
Computer Science and Engineering, ISSN : 0975-3397 Vol. 4 No. 05 May delivery”, ey.com/ca
2012
[22] T. Sato et al., ”Smart-Contract Based System Operations for Permis-
[3] KalpanaSureshchandra, Jagadish Shrinivas avadhani, ”Moving from sioned Blockchain,” 2018 9th IFIP International Conference on New
Waterfall to Agile” ,978-0-7695-3321-6/08 $25.00 © 2008 IEEE Technologies, Mobility and Security (NTMS), Paris, 2018 pp. 1-6.
[4] Bashir, I. (2018), “Mastering Blockchain” 1st ed. Birmingham, UK.: [23] S. Pongnumkul et al., ”Performance Analysis of Private Blockchain
PACKT Publishing, pp.10,12,16-23,27-32,35-38,44,359,362-373. Platforms in Varying Workloads,” 2017 26th International Conference
[5] Logica BANICA , Magdalena RADULESCU , Doina ROSCA, Alina on Computer Communication and Networks (ICCCN), Vancouver, BC,
HAGIU, “Is DevOps another Project Management Methodology?”, 2017 pp. 1-6.
Informatica Economică vol. 21, no. 3/2017, DOI: [24] Arxiv.org. Hyperledger Fabric A Distributed Operating System for
10.12948/issn14531305/21.3.2017.04 Permisioned Blockchains [online] https://arxiv.org/pdf/1801.10228
[6] Nicolás Paez,” Versioning Strategy for DevOps Implementations”, 978-
1-5386-5447-7/18/$31.00 2018 IEEE

Authorized licensed use limited to: Centro de Est. e Sistemas Avançados Recife (CESAR). Downloaded on April 01,2023 at 14:49:33 UTC from IEEE Xplore. Restrictions apply.