Features/Relational database

From TempusServa wiki
Revision as of 09:19, 10 November 2024 by Kpe (talk | contribs) (Created page with "== Usage == Since the 1960 it has been well known that SQL databases are the way to go for complex systems storage. TS is based on the MySQL / MariaDB / Percona databases, and all data is fully normalized granting multiple benefits * High performance with high volumes * Easy to integrate with BI systems * Predictable structures == Scalable applications == Applications built in TS will adhere to common design practices ensuring good performance, stability and integrity...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Usage

Since the 1960 it has been well known that SQL databases are the way to go for complex systems storage.

TS is based on the MySQL / MariaDB / Percona databases, and all data is fully normalized granting multiple benefits

  • High performance with high volumes
  • Easy to integrate with BI systems
  • Predictable structures

Scalable applications

Applications built in TS will adhere to common design practices ensuring good performance, stability and integrity.

The platform is very scalable in regard to

  • Complexity: You can keep extending the models as far as needed, using the Parent and Child relations. We even support logical constructs such as many-to-many relations.
  • Performance: TS dataases are largely unaffected by data set sizes and number of concurrent users. There builtin configurations for indexing fields, and the built in searches can be supported by Elastic search and indexing

To prove our point we have actually had the whole platform running smoothly on a Rasperry PI.

Relational searches