Skip to content

Latest commit

 

History

History
82 lines (58 loc) · 3.39 KB

principles.adoc

File metadata and controls

82 lines (58 loc) · 3.39 KB
Raw

Guiding Principles (Requirements)

Table of Contents

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in IETF BCP14 (RFC2119 & RFC8174)

SPDX-FileCopyrightText: 2023 Contributors to the Eclipse Foundation

See the NOTICE file(s) distributed with this work for additional
information regarding copyright ownership.

This program and the accompanying materials are made available under
the terms of the Apache License Version 2.0 which is available at
https://www.apache.org/licenses/LICENSE-2.0

SPDX-FileType: DOCUMENTATION
SPDX-License-Identifier: Apache-2.0

1. Use Cases

The table below helps to illustrate the various use cases for uProtocol.

Table 1. Use Cases
Category Use Case Name Description

File Transfer

Large file Transfer

Transmission of large files (>1MB) through the streamer

Small file Transfer

Transmission of small data/files (<1MB in size) either through RPC or the streamer

Events (pub/sub)

Event data

Non time sensitive event

Low latency event data

Time sensitive event

Notifications

Targeted event data

When a producer wants to notify a specific consumer of an event that occurs

RPC

Commands and Instructions

Invoking API calls in local or remote services from an application

Streaming

Video streaming

Sending captured video from one device to the next

2. Guiding Principles

Table 2. Guiding Principles
Principle Description

Service (not Signal) Oriented Architecture

  • MUST provide service oriented architecture interfaces in lieu of signal based architecture

Architecture Patterns

  • MUST support publisher/subscriber, observer (notification), and RPC architecture design patterns

  • MUST provide the same mechanism for pub/sub and RPC regardless of the device the uE runs on

Follow Clean Architecture Principles

  • MUST point dependencies inward

  • MUST provide abstraction where it makes sense

  • MUST avoid unnecessary translation/duplication

  • SHOULD support a single reflection

Declare Once, Use Everywhere

  • All types (services, resources, data structures, etc…​) MUST be declared once resulting in a single source of truth for said types

  • MUST use a common Interface Definition languages that supports majority of well known programming languages (Java, C++, Rust, C, Python, etc…​)

  • MUST describe event data in a common way such that the same message can be sent over any transport

  • MUST be able to dispatch/route messages without looking at the data (payload)

Ubiquitous Language

  • MUST expose the same interfaces regardless of the device/deployment

Dynamic Deployment

  • MUST decouple applications from services (can be independently updatable), and decouple application/services from the platform

Event Transport Abstraction

  • MUST support all common automotive use cases (defined in Use Cases)

  • MUST decouple messages from the underlining transport such that producers can be unaware of their consumers (and how the messages are transported)

Duplication of Data Is Bad

  • Batching, aggregation, queuing of events, MUST be handled by the platform such that each application and/or service, doesn’t have to do it