...

It could be a central component in a data/event architecture within one ECU (distributing data to processes / software components).  In those cases it is typical to have a direct shared memory or other internal "IPC" connection, not usually needing a IP network.

Notification features

Some databases might have some sort of "notification" feature that is used by other components directly.  Because if a Data-Server supports the subscription functionality towards its external clients, it would benefit from getting notifications from the StateStorage State Storage when a new value is received there, so that internal polling is not necessary.

However, if the component implements any more logic beyond simple subscription (notify me whenever a new value is written for this data item) then it should likely be named  named Data Server, or Event framework component (see definitions).

Sync features

Some databases might have a data synchronization component to automate sync of data between instances.

Some implementation options:
Apache IoTDB, REDIS, (sqlite), in-memory-table, Realm

...

A component that fetches data from a Data Server according to the chosen protocol. It typically interfaces with a database, OEM database or other, where it stores fetched data.

Data Synchronization Component

A component that automates the sync of data between instances. For example between Data Stores. This can include such sophisticated features as conflict resolution. Such features can be very useful when applying data centric architectures to zone and central compute electrical architectures in-vehicle. Different zones may have local zone specific State Storage that is selectively synchronized with State Storage in the central compute or TCU for further processing.

Event Framework Component

...