When services computing meets blockchain: Challenges and opportunities

Xiaoyun Li, Zibin Zheng, Hong-Ning Dai*

*Corresponding author for this work

Research output: Contribution to journalArticlepeer-review

Abstract

Services computing can offer a high-level abstraction to support diverse applications via encapsulating various computing infrastructures. Though services computing has greatly boosted the productivity of developers, it is faced with three main challenges: privacy and security risks, information silo, and pricing mechanisms and incentives. The recent advances of blockchain bring opportunities to address the challenges of services computing due to its build-in encryption as well as digital signature schemes, decentralization feature, and intrinsic incentive mechanisms. In this paper, we present a survey to investigate the integration of blockchain with services computing. The integration of blockchain with services computing mainly exhibits merits in two aspects: i) blockchain can potentially address key challenges of services computing and ii) services computing can also promote blockchain development. In particular, we categorize the current literature of services computing based on blockchain into five types: services creation, services discovery, services recommendation, services composition, and services arbitration. Moreover, we generalize Blockchain as a Service (BaaS) architecture and summarize the representative BaaS platforms. In addition, we also outline open issues of blockchain-based services computing and BaaS.
Original languageEnglish
Pages (from-to)1-14
Number of pages14
JournalJournal of Parallel and Distributed Computing
Volume150
Early online date1 Jan 2021
DOIs
Publication statusPublished - Apr 2021

User-Defined Keywords

  • Services computing
  • Blockchain
  • Security
  • Smart contract
  • Blockchain-as-a-Service

Fingerprint

Dive into the research topics of 'When services computing meets blockchain: Challenges and opportunities'. Together they form a unique fingerprint.

Cite this