Page History

...

• Address two high level implementation needs, keeping in mind a path towards production where possible:
  1. Easy to develop: make it easy to build, modify and trial by providing an instance running on a host, e.g. using Docker container(s).
  2. Closer to production: the same base code should be deployable on automotive hardware (or its simulation), e.g. Yocto, container orchestration, SOA etc.
• A generic code base for the basic building block should allow flexible compilation to meet those needs on x86 and ARM. The target for how it is used being a matter of deployment at a high level.
• Follow the OSS mantra of adopt where you can, extend if needed, create where necessary.

What?

• At its core the service has features in three key areas:

...

• It is recognised that additional features, such as synchronisation are absolutely desirable and have been a part of discussions in the Data Architecture group. For this proposal a base feature set is described to help readers quickly grasp the concept. If the proposal proceeds then additional details will be created collectively based on interest and participation.

• As a starting point it is suggested that the Service could be realised as a basic building block combining VISS Data Server with highly functional VSS Data Store.
• With some supporting documentation that would help meet the ongoing request from newcomers to the VSS eco-system as to how it can be used.
• At the same time piece of Lego This piece of lego can then be extended and reused in various ways.
  • The Data Architecture group for instance has various topics it wishes to investigate related to data-centric architectures.
• Details in the following sections.

...