Transbase® Edge & previous versions

Transbase® Edge V. 8.4 (2020)

Transbase® Edge V. 8.4 contains optimizations, extensions and bug fixes to those already published in V. 8 and the additional functions

  • Data import / export via JSON files
  • SQL / PSM (Persistent Stored Modules) = programming language in the core

Transbase® Edge V. 8.3 (2019) - Crowd

V. 8.3 extends Transbase® Edge with the Crowd functionality, which allows a loose network of Edge databases to be formed in any hierarchy level (Edge Node -> Parent -> Root) with any nesting and cascading. Inquiries to the root or parent database are distributed to all connected edge or other parent databases, and the returned results are collected and aggregated.

Additional innovations are:
  • In-memory tables
  • New SQL functions (variance)
  • IO optimization by means of background activities (logging, writing through the DB)
  • own FLUSH DATABASE command for programs

Read more about the Crowd functionality.

Transbase® Edge V. 8.2 (2019)

Transbase® Edge V. 8.2 contains optimizations, extensions and bug fixes to those already published in V. 8 as well as the additional functions

  • Math and Statistical Capabilities Extension according to SQL Standard
  • JSON Import and Export Functions
  • Use of Hardware-Based Cryptographic Encryption if available
  • Export for other platforms (switching from little-endian to big-endian and vice versa)

Transbase® Edge V. 8.1 (2017) - SPA & Microservices

Transbase® Edge (from V. 8.1) is the extension of Transbase® Mobile for IoT Devices. It is general available from November 2017 and can be distinguished by its Single Process Architecture (SPA) and new Functionality, esp. for the support of mobile Applications and Edge Computing (IoT). 

Thanks to the new Single Process Architecture (SPA), Transbase® Edge can be operated as an IoT Database. It is only known and available for a single application, does not need system-wide service and is firmly integrated into the application process as a Microservice.

Transbase® Edge is a very good choice to restrict external access to the Database to a single Application. Transbase® Edge extends platform support for Android and iOS, allowing Transbase® to run on smartphones or tablets.

This means:
  • Now for every Client connection a dedicated Thread is responsible within Transbase®.
  • The database-specific shared memory is replaced by memory within Transbase®.
  • The former tbadmin services are produced through new SQL commands.
  • Administration functions can now be used over the network. 
 The advantages of this new Single Process Architecture (SPA) are:
  • essentially simpler process structure: 
         When the process transbase is started, the complete functionality is provided. 
         Upon completion of the process, all database services are terminated. 
        As in the past, individual databases can be individually booted and shut down.
  • more efficient starting and stopping of new client connections
  • faster and easier communication and synchronization between threads
  • possibility to operate Embedded Databases as Microservices
Following features are implemented:
  • Microservices:
    A Connect to Transbase® Edge creates a dedicated thread in the Application that implements the Database operations (see image). Also, several connections in multiple threads and the multiple operation of Transbase® are possible within a single Application. Transbase® Edge is a good way to restrict external access to the database to a single application. This is indispensable esp. for the operation of Transbase® on smartphones or tablets.
  • New platforms:
    In the course of the change of the system architecture, many unification procedures were realized, so that the portability of Transbase® could be further improved. Transbase® is now LSB 4.1 compliant.
    As new platforms are now available: Android, iOS, Raspberry Pi as well as all previous server platform. The server platforms support all Linux, UNIX, BSD, Windows and Solaris derivatives as well as MacOS.
  • Protocol optimization:
    For a common class of queries (one-row-selects) a significant protocol change has been made so that now only a round trip is needed. This leads to a considerable improvement in the performance, in particular in the case of slow conductors. Comparable protocol optimizations could be implemented in distributed transactions.

Transbase® Edge is ideally suited to restrict external access to the database to a single application. Transbase® Edge extends the platform support for Android and iOS and thus the operation of Transbase® on smartphones or tablets. The use of Transbase® Edge in an embedded environment offers numerous advantages in terms of efficiency, robustness, performance, reusability, modularization and security. Thanks to the consistent transaction concept, software products can be developed in a completely different quality level.

Despite unrestricted and comprehensive functionality, the complete footprint (code and system data) is less than 2 Mbytes with appropriately adapted installation and configuration.

Since all Transbase® interfaces remain identical, classic PC applications based on Transbase® can also be easily ported to embedded platforms without modifications. Applications and data can be used unchanged on these platforms.

Important: ELS for V. 7.1.2 and earlier

Transbase® Edge (from V. 8.1) is available since November 2017. This means for all available previous versions of Transbase® that Access, Maintenance and Support will only be available including ELS.

We recommend upgrading from older versions (V. 7.1.2 and earlier) to V. 8. Information about significant changes of the single versions and the associated conversion effort can be found here. Please also read our Transbase® V. 8.1 Release Note.

You need help converting to a newer version? Then please contact us for appropriate consulting services.

Transbase® V. 7.1.2 (2014)

With Transbase® V. 7.1.2, the direct support of the native 64-bit architecture enabled a considerable increase in performance compared to the previous version V. 6.9.

Following features are implemented:
  • Use of larger caches:
    The use of larger caches (64bit Architecture), which results from the absence of the 4 GB limitation of 32bit systems, also allows the complete operation of very large databases in the main memory and thus significant speed advantages.
  • User-specific namespace:
    Transbase® V. 7.1.2 has been extended by a user-specific namespace. Two users Max and Moritz can create a table T to which they can access either T or Max.T or Moritz.T. This greatly simplifies the operation of many users (web applications) that are separated from each other.
  • Advanced Communication:
    In addition to the TCP / IP communication between the client and the server in the network, Transbase® V. 7.1.2 also has pipe communication. This simplifies interprocess communication between applications and servers on the same computer. In addition, pipes offer improvements in the communication speed, especially in connection setup.
  • Improved Replication:
    Transbase® V. 7.1.2 provides further improvements to replicated Databases: Semi-synchronous and synchronous replication allows redundancy to improve load distribution and increases data loss protection. As a new addition, Replication is now also available for Transbase® CD.

Please also read our Transbase® V. 7.1.2 Release Note. For further information, please visit our Info-Center or contact us.

Transbase® V. 6.9 (2012)

Transbase® V. 6.9 provides functional enhancements such as dataspaces, SQL extensions, replication (Transbase® CD), and performance enhancements for multi-core CPUs that deliver significant performance gains.

The replication of master databases to several slave databases is controlled by the new process tbrepl.

The Slave Databases are read-only and can be used either as a hot backup or as a dynamic load distribution. For this purpose, a so-called database grid can be set up. A Transbase® server can now be configured so that no static TCP ports, but only two static ports are used. This allows Transbase® to be operated more easily behind a firewall.

Transbase® CD has been expanded by so-called generation deltas. Changes on a Transbase® CD database are combined into highly compressed, even realtime distributable deltas. The import of the deltas is robust and requires little or little further copying and CPU expenditure, depending on whether one wants to minimize the Einspielzeit or the transfer volume.

The Transbase® SQL Core System has been extended by Dataspaces to reduce the fragmentation of pages. The new WITH clause allows the formulation of partial results for use in a subsequent query. In addition to the previously known BLOBs, CLOBs are now available, which can only contain CHARACTER texts. CLOBs are treated as strings, i. possibly code converted. CLOBs can be fully-text-indexed.

The parallel processing of queries using dynamically controlled threads has been extended and improved. IO jobs can now be processed in parallel, which in particular promises a considerable performance improvement for RAID systems. The database cache is divided into several partitions (up to 128), which are blocked independently and thus significantly increase throughput in parallel operation.

Please also read our Transbase® V. 6.9 release note and Transbase® Update Distribution and Replication (V. 6.9 and later).