Table of Contents
Fetching ...

Standardizing Access to Heterogeneous Quantum Backends: A Case Study on Cloud Service Integration with QDMI

Patrick Hopf, Sebastian Stern, Robert Wille, Lukas Burgholzer

TL;DR

A case study demonstrating the integration of QDMI with Amazon Braket, a quantum computing cloud service that provides a single access point to a wide range of hardware technologies, paving the way for integrated access to cloud-hosted quantum resources from QDMI-enabled software stacks.

Abstract

With an increasingly diverse portfolio of quantum backends, the adoption of standardized interfaces has become a key prerequisite for scalable access and interoperability within quantum software stacks. The Quantum Device Management Interface (QDMI) addresses this challenge and is emerging as one of the de facto standards for hardware abstraction, enabling the unified management not only of individual Quantum Processing Units (QPUs) but also of complete full-stack cloud services. This paper presents a case study demonstrating the integration of QDMI with Amazon Braket, a quantum computing cloud service that provides a single access point to a wide range of hardware technologies. By treating the cloud service itself as a unified device, the proposed implementation enables management of the complete task lifecycle - ranging from authentication and circuit submission to result retrieval - across Braket's heterogeneous set of simulators and hardware backends. We detail the engineering insights gained from this integration and present a hands-on example workflow, ultimately paving the way for integrated access to cloud-hosted quantum resources from QDMI-enabled software stacks.

Standardizing Access to Heterogeneous Quantum Backends: A Case Study on Cloud Service Integration with QDMI

TL;DR

A case study demonstrating the integration of QDMI with Amazon Braket, a quantum computing cloud service that provides a single access point to a wide range of hardware technologies, paving the way for integrated access to cloud-hosted quantum resources from QDMI-enabled software stacks.

Abstract

With an increasingly diverse portfolio of quantum backends, the adoption of standardized interfaces has become a key prerequisite for scalable access and interoperability within quantum software stacks. The Quantum Device Management Interface (QDMI) addresses this challenge and is emerging as one of the de facto standards for hardware abstraction, enabling the unified management not only of individual Quantum Processing Units (QPUs) but also of complete full-stack cloud services. This paper presents a case study demonstrating the integration of QDMI with Amazon Braket, a quantum computing cloud service that provides a single access point to a wide range of hardware technologies. By treating the cloud service itself as a unified device, the proposed implementation enables management of the complete task lifecycle - ranging from authentication and circuit submission to result retrieval - across Braket's heterogeneous set of simulators and hardware backends. We detail the engineering insights gained from this integration and present a hands-on example workflow, ultimately paving the way for integrated access to cloud-hosted quantum resources from QDMI-enabled software stacks.
Paper Structure (16 sections, 3 figures, 1 table)

This paper contains 16 sections, 3 figures, 1 table.

Figures (3)

  • Figure 1: Illustration of the Munich Quantum Software Stack, showcasing the separation of concerns across frontend, middle, and backend layers. QDMI serves as a standardized abstraction for managing heterogeneous quantum backends, including local devices, simulators, and cloud-hosted resources.
  • Figure 2: High-level flow of running quantum programs on the Amazon Braket service from a local user environment through Braket and S3 client instances provided by an AWS SDK wrapping service APIs and handling the authentication of API calls: A quantum circuit is submitted for execution on a target device using BraketClient::CreateQuantumTask (1). The Braket service validates, compiles, optimizes, queues and schedules the circuit for execution on the target device (2). Task state and queue position can be queried with BraketClient::GetQuantumTask (3). Upon task completion, Braket stores the result in a user-defined location on Amazon S3 (4). The result object can be downloaded with S3Client::GetObject (5) using the object key returned in the BraketClient::GetQuantumTask response.
  • Figure 3: Sequence diagram illustrating the interaction between the client and the Amazon Braket QDMI Device across the stages of setup, session management, job management, and cleanup. Some intuitive responses are omitted for readability.