Ozy: A General Orchestration Container
Glenn Osborne, Tim Weninger

TL;DR
Ozy introduces a flexible, technology-neutral orchestration container that relaxes traditional constraints, enabling simpler and more feature-rich distributed applications beyond standard business process models.
Contribution
The paper presents Ozy, a novel general orchestration container that broadens service orchestration beyond traditional business process standards like BPEL.
Findings
Ozy relaxes many traditional orchestration constraints.
Supports a wider range of service motivations like XaaS and RMAD.
Enables simpler, more feature-rich distributed applications.
Abstract
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…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
