On this page you may get overview of main definitions used in the TimeBase universe
Click Tag to Display Pages: definitions tbd

TimeBase is a high-performance event-oriented time-series database with embedded data modeling and serialization functionality, streaming system and messaging middleware developed by EPAM Real Time Computing Lab (former Deltix).

Message - A message describes a specific event, and is stored or edited as a unit. Every message in TimeBase is automatically associated with a moment in absolute time and an entity key. The entity is an abstract concept that identifies the object, to which the event relates the most. A message contains number of data fields according to the message structure. There are two required fields - a symbol (sometimes called key), and a timestamp.
More Info

  • Symbol - a key that describes a specific time-series (e.g. in IoT it may be a sensor id, or trading activity for specific security).

Class Definition - describes structure of a message. The class definition lists the fields included in messages of this class, along with their names, data types, limits, and precision.
More Info

Content Class - a class that describes messages that are expected in a stream.

Instrospector - API to create class hierarchy from specific Java or C# class definitions More Info.

Stream - a collection of messages ordered by time with predefined structure.
More Info

  • Polymorphic Stream - a stream containing messages of several classes.
    More Info
  • Fixed Type Stream - a stream containing messages of a single specific class.
    More Info
  • Durable Stream - persistent stream which can store messages on any storage.
    More Info
  • Transient Stream - in-memory stream is not persisted anywhere. Messages are stored in a memory buffer, which acts as a queue with one tail and multiple heads.
    More Info
  • Unique Stream - a stream (Durable or Transient) that supplies a copy of last-known values for each symbol to new stream subscribers.
    More Info

Topic - a high-performance messaging channel that directly connects data Producers and Consumers (via UDP or IPC).
More Info

Loader - API for data producers. Publishes messages into TimeBase streams.
More Info

Cursor - API for data consumers. Reading data from one or many TimeBase streams according to the subcriptions.
More Info

Live Cursor - Reading data ‘live’ from one or many TimeBase streams.
More Info

Data Cache - LRU cache in memory for TimeBase data.
More Info

Inheritance - Message classes can inherit from other message classes. TimeBase supports single inheritance only, just like Java and C#. The inheritance hierarchy forms a tree-like structure. Nested classes are not currently supported.

Space - data partition