JSON-RPC 2.0

A JSON-RPC 2.0 is a remote procedure call protocol that enables standardized data exchange (between distributed systems over network connections).

• AKA: JSONRPC 2.0, JSON Remote Procedure Call 2.0.
• Context:
  • It can establish Structured Communication through json message formats.
  • It can enable Remote Method Invocation through http transport or tcp connections.
  • It can support Bidirectional Communication through request-response patterns.
  • It can maintain Protocol Compatibility through version identifiers.
  • It can handle Error Reporting through error objects.
  • ...
  • It can often implement Batch Processing through message arrays.
  • It can often provide Asynchronous Operations through notification messages.
  • It can often facilitate Service Discovery through method listings.
  • It can often support Session Management through connection states.
  • ...
  • It can range from being a Simple Request-Response System to being a Complex Distributed Application Protocol, depending on its implementation scope.
  • It can range from being a Basic Message Parser to being an Advanced Communication Framework, depending on its feature integration.
  • ...
  • It can integrate with Web Service for http-based communication.
  • It can connect to Message Queue for asynchronous processing.
  • It can support API Gateway for service routing.
  • ...
• Example(s):
  • Transport Implementations, such as:
    • HTTP Transports, such as:
      • RESTful JSON-RPC for web api integration.
      • WebSocket JSON-RPC for real-time communication.
    • TCP Transports, such as:
      • Raw Socket JSON-RPC for direct network communication.
      • TLS JSON-RPC for secure data exchange.
  • Message Patterns, such as:
    • Request Types, such as:
      • Method Call Request for remote procedure invocation.
      • Notification Request for one-way messaging.
    • Response Types, such as:
      • Result Response for successful execution.
      • Error Response for failure handling.
  • ...
• Counter-Example(s):
  • XML-RPC, which uses xml format instead of json format.
  • REST API, which uses resource-based architecture instead of procedure-based architecture.
  • SOAP Protocol, which requires xml schema definition and wsdl contract.
• See: Remote Procedure Call, JSON Format, Network Protocol, Distributed Computing, API Design.

---

---