Announcing eXtremeDB/rt 2.1! Advanced flash simulation, smaller footprint and embedded connectivity.
Learn more
Hard real-time database for Advanced Driver Assistance (ADAS)
Sensor data fusion demands a hard real-time database management system.
An ADAS-equipped car is outfitted with many sensors of many types; SONAR, LIDAR, RADAR, optical cameras, GPS and more. These sensors support functions such as traffic sign recognition, lane-keeping (or lane departure warning), adaptive cruise control, parking assist, blind spot detection, collision avoidance and beyond. Let’s not forget internet connectivity for traffic data, maps, and road works.
The view these sensors collectively provide is not static. For example, a car traveling slowly in the city will collapse the information bubble to emphasize points-of-interest, intersections and such. Conversely, a car traveling faster needs to look out farther ahead and, for path prediction, shouldn’t be overly concerned about intersections ahead that the car cannot navigate kinetically because of the nearness of the intersection and the car’s speed.
At its core, this is sensor data fusion. All of this data needs to get to a central location, a database, so that it can be aggregated, correlated, analyzed and acted upon, all in real-time.
Many of these subsystems are time-critical, such as collision avoidance, distance-keeping and path prediction. The logical extension of this is that the database for ADAS systems must be real-time.
Learn more about Asymmetric MultiProcessing (AMP) with eXtremeDB.
A reliable database system built with safety in mind
eXtremeDB/rt is the first commercial-off-the-shelf (COTS) embedded database system to enforce database transaction deadlines, making it uniquely suitable for embedded systems with hard real-time constraints, and the only commercially supported hard real-time database for advanced driver assistance systems.
Like conventional eXtremeDB, eXtremeDB/rt is an ACID compliant database system that provides services for the storage, retrieval and manipulation of data. The differences lay in the temporal requirements of the managed data, transaction scheduling policies and the timing constraints on transactions.
AUTOSAR Compliant
Offering hybrid storage built on a true in-memory database system, eXtremeDB has always taken responsibility for memory management. As an embedded database system, eXtremeDB creates no processes or threads, and has never had any dependencies on the operating system or C runtime library. It’s compatible with a number of the principles embodied in AUTOSAR such as disassociation from the underlying hardware and the actual operating system (or lack thereof) thus no OS-based memory management, no threads/processes, and no kernel-based synchronization primitives.
Read the press release, “eXtremeDB 8.1 Supports Several Principles of AUTOSAR
Watch “Database System Requirements to Achieve Level 3+ Autonomous Driving” presented by McObject at the EETimes Advanced Automotive Tech Forum, or contact us to discuss your project if you need a database for ADAS.
Why should you consider eXtremeDB/rt?
eXtremeDB/rt is founded on eXtremeDB, the first DBMS created specifically for embedded systems, with over 20 years and 10s of millions of systems deployed. eXtremeDB/rt was developed to work hand-in-glove with deterministic real-time tasks.
Data management for real-time systems
The eXtremeDB/rt kernel — the transaction schedulers, recovery algorithms and the database access API — adjusts to limited operating system services and strives to compensate for their conservative nature by optimizing performance and memory footprint of the database management components.
High Priority Earliest Deadline First Transaction Scheduling
The eXtremeDB/rt EDF-TM (Earliest Deadline First Transaction Manager) implements a wait-list of transactions, in other words a “transaction queue” in the database kernel. Transaction requests are sorted first on their priority and then within the same priority by deadline.
Priority Inheritance (PI) Transaction Scheduling
The Priority Inheritance Transaction Manager exploits the underlying real-time operating system’s scheduling, and may temporarily raise the priority of a thread that is blocking a higher priority thread to let it finish the transaction faster, so it can get out of the way.
eXtremeDB for Asymmetric MultiProcessing (AMP)
An AMP system has multiple CPUs, each of which are a different architecture. Each CPU has its own address space (though some of the memory may be shared with other cores). For example, NXP i.MX8x with embedded Linux on the ARM Cortex-A and FreeRTOS or Vector’s MicroSAR on the ARM Cortex-M4.
Ideal for sensor data fusion, etc.
Review the white paper,
Shared Data in Asymmetric Multiprocessing (AMP) Configurations.
eXtremeDB for HPC
- Columnar and row-oriented storage to optimize time series data
- A library of more than 150 built-in functions
- Sharding for elastic scalability
- Distributed query processing
eXtremeDB Embedded
- ACID-compliant transactions
- Type-safe API
- Transaction logging
- Tiny footprint
- High availability options
- Bidirectional Replication
- Mitigates loss of data due to connectivity issues
- Multi-tier replication (e.g. edge-to-gateway-to-gateway-to-cloud)
- Compression to maximize limited bandwidth networks
eXtremeDB/rt
- Deterministic ACID-compliant transactions
- Adaptable real-time transaction managers
- No restrictions on execution patterns
- A highly configurable database kernel
- Support for all major commercial RTOS
- Ideal for ADAS or SCADA