Category: Cloud Computing Copyright © 2018, IGI Global. Copying or distributing in print or electronic forms without written permission of IGI Global is prohibited. 1040 DOI: 10.4018/978-1-5225-2255-3.ch091 Clouds of Quantum Machines INTRODUCTION This work is a continuation of studies started at 2014. Since then, I improved some ideas about theoretical quantum machines interacting in cloud operation, as well as enhancements on the concept of quantum entanglement itself. Some recent works have been added to the original references, although the classic treatises remain in effect, given the slowness with which the subject progresses. As we know, one of the great challenges in quantum computing is how to preserve quantum entanglement, since microphysical systems are extremely sensitive to external disturbances. It is one of my aims to show a way to minimize this problem. Moreover, a quantum orchestration metalanguage is introduced into a first schematic representation of the operation of a quantum cloud aiming to optimize further constructions of quantum algorithms. While it is essential that the reader becomes familiar with quantum mechan- ics, some parts of my first work are reproduced here in order to reduce the effort to understand the subject. BACKGROUND: SERVICES AND CLOUDS IN A CONTEMPORARY APPROACH Services are cybernetic replicas of human prac- tices, being evoked by well-established environ- mental motivations. In turn, SOA is an architecture that integrates in a standard manner several service units, each of them sending their features as sets of tasks over the network. Only service interfaces are exposed to consumers as exported methods (Nakamura et al., 2004). Therefore, when services are requested, SOA seeks the best responses to those environmental motivations according to the internal logic of each service. In particular, this architecture is now strongly linked to the theme of “enterprise application integration” (EAI) in contexts where legacy applications already established are performed on different platforms. The literature on SOA comprises several mile- stone contributions as the works of Nakamura et al. (2004), Erl (2005), Anderson & Ciruli (2006), Natis (2007), Sha (2007) and, markedly, Frenken et al. (2008) about device-level service deployment. On this latter subject, it is noteworthy that, in the process of architectural development, devices which access legacy applications are created and interact using a protocol defined by the system. In turn, the system returns the aggregated information from the various legacy applications, preferably without any additional code. The architectural de- velopment also takes care of the service interface, prescribing the information required to access the competences of that. It is worth remembering that the existence of interfaces and descriptions of ac- cessibility is sine qua non for the implementation of SOA. More recent works show the state-of-art in services orchestration (MEF Forum, 2015; Lemos et al., 2015). In SOA projects, the so-called Enterprise Service Bus (ESB) is thought to be the main component of the infrastructure layer. It is the mediator between provider and service consum- ers, and its responsibility is to provide integration and interoperability between different systems. Embedded in this responsibility is also the mission of cleaning the databases by a service that tracks and recognizes all of the systems which shall be linked. Connectors are created in the databases feeding a new datawarehouse completely normal- Nilo Sylvio Serpa Universidade Paulista, Brazil