1. Embedded realtime DBMS

Option eXTreme from McObject

Features:
~ In-memory; no file system required
~ Embedded (not a client/server architecture)
~ Blazingly fast – in-memory embedded architecture yields micro-second transactions, even on modest hardware
~ High availability, implemented via a time-cognizant two-phase commit protocol
~ Optional transaction logging module for persistent data
~ Optional SQL interface
~ Tiny code size, starting from just 50 KB
~ Very efficient storage manager – typical overhead is just 15-40 percent (meaning 1 MB of data needs just 1.15 – 1.4 MB of memory)
~ No dynamic memory allocation; suitable for the most stringent safety requirements
~ Highly portable; written in ANSI C, with no dependence on C run-time library; eXtremeDB can even run without an RTOS!
~ XML interface to simplify data exchange with other XML-enabled systems
~ Developer friendly – creates a type-safe, intuitive programming interface with extensive checking to speed development

References:
~ Boeing/Apache Longbow helicopter
~ Within Apache Longbow, eXtremeDB will manage secure, digitized battlefield data
~ eXtremeDB’s XML interface will facilitate communications, both internally and
~ between attack helicopter and external (ground and air) systems
~ Embedded software including eXtremeDB will run on airborne PowerPC processors and
~ a commercial real-time operating system (RTOS)
~ program is being developed by Boeing Company’s Phantom Works organization in Mesa, Arizona
~ eXtremeDB High Availability Edition provides highest degree of reliability for Apache’s mission-critical systems
~ eXtremeDB’s streamlined design and in-memory deployment deliver near-zero-latency responsiveness
~ required for advanced systems like a combat helicopter
~ Apache Longbow is world's only fourth-generation attack helicopter and
~ only combat helicopter in service with ability to
~ rapidly detect, classify, prioritize and engage stationary or moving enemy targets
~ at standoff ranges in nearly all weather environments

2. Network-centric DBM:
~ manages command & control data, mission data, digital maps, network resources in area
~ keeps updated resource data such as information about Base4Xis, other Xi s and Sensor4Xis

3. Server DBM:
~ stores, processes and updates sensor data, which Xi collects and which sensor DBMS sends
~ readies sensor data for downloading to Base4Xi
~ optionally makes data ready to be uploaded to network, if Xi operates without any Base4Xi
~ links: XTree for internet sensors , Sensor databases , Apache Xindice , Oracle , MySQL , Berkeley Database Research , XPath , XUpdate

4. Sensor DBM:
~ manages data collected from all sensors embedded inside Xi
~ empties database once data has been moved to server database
~ links: managing Sensor Data freshness , Sensor databases , TinyOS/TinyDB
~ more: Sensor networks as a distributed database system , Join in sensor network , Power aware routing for sensor databases

5. Mobile base station DBM:
~ industry standard mobile base station DBMS, which exists only, if mobile base station is embedded inside Xi

6. Mobile phone DBM:
~ industry standard mobile phone DBMS, which exists only, if a mobile phone is embedded inside Xi
~ Android based DBMS