Cloud API Entrypoint for Multi-Tenant Service Extension
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current cloud computing systems lack a seamless method to extend services and functionalities in a multi-tenancy-compatible fashion, particularly in distributed, virtual data centers, due to limitations in access control and integration of new services with existing multi-tenancy infrastructure.
Innovation Solution
The implementation of a cloud application programming interface (API) entrypoint with a service-extension interface and authorization-service management interface, allowing service extensions to obtain authorization indications for requests and processing these requests through a cloud API entrypoint server that dispatches them to service-extension servers, while utilizing an extension filter for distributing HTTP requests and responses among computational entities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a cloud API entrypoint with service-extension interface is implemented, then service extension capability is improved, but system complexity increases
Solution Approach 1:
The system is divided into distinct components: cloud API entrypoint server, service extension servers, authorization service, and extension filters. Each component has a specific responsibility, allowing service extension functionality to be added without complicating the core system. The segmentation enables independent development and deployment of service extensions.
Solution Approach 2:
An authorization service acts as an intermediary between service extensions and multi-tenancy infrastructure. This mediator handles access control and authentication, allowing service extensions to be integrated without directly complicating the core system architecture. The extension filter serves as another intermediary that intercepts and routes requests appropriately.
2Reliability
If authorization service is integrated for access control, then security is improved, but processing time increases
Solution Approach 1:
Authorization checks are performed preliminarily in the extension filter before requests are forwarded to service extension servers. By validating authorization early in the request lifecycle, the system ensures security without requiring repeated checks later in the processing chain, thus minimizing time loss.
Solution Approach 2:
The authorization service operates autonomously, maintaining its own state and making independent decisions about request authorization. This self-service capability reduces the need for complex coordination with other system components, streamlining the authorization process and reducing processing time.
3Productivity
If service extensions are distributed across multiple servers, then system scalability is improved, but coordination complexity increases
Solution Approach 1:
The cloud API entrypoint server serves multiple functions: it acts as a universal entry point for all requests, coordinates service extension dispatching, and manages communication between distributed service extension servers. This multi-functionality reduces the need for additional coordination infrastructure, simplifying the distributed system architecture.
Solution Approach 2:
The system implements feedback mechanisms where service extension servers report status and results back to the cloud API entrypoint server. This feedback loop enables centralized coordination without requiring complex peer-to-peer communication between distributed servers, reducing coordination complexity while maintaining scalability.
Data Source
AI summary
The current document is directed to an interface and authorization service that allows users of a cloud-director management subsystem of distributed, multi-tenant, virtual data centers to extend the services and functionalities provided by the cloud-director management subsystem. A cloud application programming interface (“API”) entrypoint represents a request/response RESTful interface to services and functionalities provided by the cloud-director management subsystem as well as to service extensions provided by users. The API entrypoint includes a service-extension interface and an authorization-service management interface. The cloud-director management subsystem provides the authorization service to service extensions that allow the service extensions to obtain, from the authorization service, an indication of whether or not a request directed to the service extension through the API entrypoint is authorized. Requests for service-extension URIs within the API entrypoint are processed by a cloud API entrypoint server that dispatches requests, in a predetermined order, to service-extension servers.