V2X-Based Event Acquisition and Reproduction Architecture with Event-Sourcing

Abstract

Currently, many levels of autonomous driving are being rapidly developed and are near deployment. No human intervention is required above level 4 of autonomous driving. Imperatively, a method for preventing and reproducing accidents that may occur during autonomous driving is desirable. In this study, the state change that occurs in V2X (vehicle to everything) environment is treated as first-class data to examine the cause by reproducing the accident when an accident occurs. We propose a framework that reproduces and restores state using event sourcing techniques that store first-class data. CCS Concepts • Computer systems organization ➝ Architectures ➝ Other architectures➝ Data flow architectures.

Event‐sourced, observable software architectures: An experience report

“…Before doing this exercise, our investigation first proposes a definition of observability that is as general as possible and that is not directly ascribed to the world of self-adaptive and distributed applications. Our main outcome is that designing and catering for observability require specific and granular architectural solutions such as event sourcing, [13][14][15] that can be concisely exemplified as "Capture all changes to an application state as a sequence of events" * . Event sourcing enables the continuous, incremental, and iterative improvement of the service functionalities in a DevOps fashion 16 by making service operations and their state explicit, in the form of analyzable event traces.…”

“…17 At the same time, however, designing for observability and adopting event sourcing are hard at best and represent, to date, a trial-and-error endeavor, with little to no reference approaches, tools, and techniques for designers to practically exploit as well as a myriad of possible problems. 14,15 In fact, event sourcing has always been described in general terms and it has not been accompanied by a formal definition.…”