JOIN/SIGN UP
Already a Member? |
GET INVOLVED
Understanding and Engaging in COVESA Expert Groups & Projects |
COLLABORATIVE PROJECTS
HISTORICAL
SDV Telemetry Project - On Hold |
...
Tech Stack overview
B) What, in your view, are acceptable choices (and preferred choices)
for programming languages and runtimes:
- In-cloud
- In-vehicle
Today's ECUs | Next-stage ECUs (domain controllers, central computers) | Cloud |
---|
(computers not in-vehicle) | Development tools, code-generators, converters etc. | "Vehicle cloud computing" | |||
---|---|---|---|---|---|
Python | |||||
Go | |||||
C | |||||
C++ | |||||
Rust | |||||
Javascript / NodeJS | |||||
Java | |||||
.NET, C#, ... | |||||
Haskell, Erlang, ... |
C) In existing architecture pictures (e.g. CCS), and framework implementations (e.g. iot-event-analytics/vehicle-edge/KUKSA.val, AOS) which interfaces:
- are documented
- need to be documented
- do NOT need to be documented (= internal / implementation detail)
Inspiration from these architecture pictures and other pages:
...