Peer-to-Peer API Communication via Service Daemon
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing approaches to API communication are limited by reliance on central servers, which restrict mobile devices to available server functionality, create bottlenecks, and fail to enable peer-to-peer discovery and hosting of API servers on mobile devices.
Innovation Solution
Implementing peer-to-peer API communication between mobile devices, where one device can initiate a service request, query, and complete a service independently of a central server, using a service daemon to discover and invoke APIs on other devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If peer-to-peer API communication is implemented between mobile devices, then device functionality and communication efficiency are improved, but system complexity increases
Solution Approach 1:
A service daemon is introduced as an intermediary component that manages API communication between devices. The service daemon handles service discovery, API invocation, and communication coordination, thereby enabling peer-to-peer functionality without requiring complex application-level implementation. This mediator approach resolves the contradiction by providing sophisticated peer-to-peer capabilities while keeping the application code simple.
Solution Approach 2:
The system is segmented into distinct functional components: service daemons running on each device, API servers hosting services, and communication protocols. This segmentation allows each component to be optimized independently and simplifies the overall system architecture by distributing functionality across multiple independent units rather than requiring a monolithic complex system.
2Productivity
If peer-to-peer communication is implemented, then central server bottlenecks are eliminated, but device processor load increases
Solution Approach 1:
The service daemon implements partial action by selectively initiating communication only when services are actually needed. Rather than maintaining continuous active connections or constantly polling for services, the system performs targeted API invocations based on actual service requirements, thereby reducing unnecessary processor activity while still achieving efficient peer-to-peer communication when needed.
3Adaptability or versatility
If service discovery is implemented between devices, then API functionality availability is improved, but communication overhead increases
Solution Approach 1:
Service discovery is performed as a preliminary action before actual API invocation. The service daemon on each device maintains a registry of available services and their locations, allowing devices to quickly determine service availability without requiring extensive runtime communication. This preliminary service discovery eliminates the need for repeated service location queries during actual API calls, thereby reducing communication overhead while maintaining comprehensive API functionality availability.
Data Source
AI summary
Computing platforms, methods, and storage media for application programming interface communication, for example peer-to-peer API communication, are disclosed. Exemplary implementations may: initiate, at an apparatus, a service request via a peer-to-peer API call from the apparatus to a recipient device; transmit, from the apparatus, a query to the recipient device whether the recipient device is able to fulfill the service request via an API implementation on the recipient device corresponding with an API implementation on the apparatus; receive, at the apparatus, a confirmation from the recipient device that the recipient device is able to fulfill the service request; and initiate completion of a service associated with the service request based on receipt of the confirmation of ability to fulfill the service request.