Ozy: A General Orchestration Container
This addresses the need for more flexible service orchestration in cloud computing, particularly for emerging paradigms like XaaS and RMAD, though it appears incremental as it builds on existing technology.
The paper tackles the restrictive view of services as business processes in service-oriented computing by introducing Ozy, a general orchestration container that treats services as technology-neutral, loosely coupled procedures, resulting in simpler and more feature-rich applications.
Service-Oriented Computing is a paradigm that uses services as building blocks for building distributed applications. The primary motivation for orchestrating services in the cloud used to be distributed business processes, which drove the standardization of the Business Process Execution Language (BPEL) and its central notion that a service is a business process. In recent years, there has been a transition towards other motivations for orchestrating services in the cloud, {\em e.g.}, XaaS, RMAD. Although it is theoretically possible to make all of those services into WSDL/SOAP services, it would be too complicated and costly for industry adoption. Therefore, the central notion that a service is a business process is too restrictive. Instead, we view a service as a technology neutral, loosely coupled, location transparent procedure. With these ideas in mind, we introduce a new approach to services orchestration: Ozy, a general orchestration container. We define this new approach in terms of existing technology, and we show that the Ozy container relaxes many traditional constraints and allows for simpler, more feature-rich applications.