Transbase® Edge & previous versions
Transbase® V. 8.3 available from September 2019
V.8.3 extends Transbase® Edge with the Crowd functionality, which allows for a loose combination of databases. Requests to the crowd database are distributed to all connected edge or other crowd databases, whose query results are collected and aggregated. Important to know is: The data do not leave their place of origin. Crowd databases can be nested and cascaded.
You can see a showcase for the use of the crowd function in the field of connceted car here.
Transbase® Edge V. 8.2 available from May 2019
Transbase® V. 8.2 mainly contains the following extensions:
- Math and Statistical Capabilities Extension according to SQL Standard
- JSON Import and Export Functions
- Use of Hardware-Based Cryptographic Encryption if available
- In-memory tables
- Export for other platforms (switching from little-endian to big-endian and vice versa)
Transbase® Edge V. 8.1 (ELS for V. 7.1.2 and earlier)
Transbase® V. 8.1 is available since November 2017. This means for the available previous versions of Transbase®:
- V. 7.1.2 and earlier: support will only be available through ELS Support
We recommend upgrading from older versions (V. 7.1.2 and earlier) to V. 8.1.
Information about significant changes of the single versions and the associated conversion effort can be found here.
You need help converting to a newer version? Then please contact us for appropriate consulting services.
Transbase® Edge V.8.1
The new version Transbase® Edge 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.
The use of Transbase® Edge in the embedded environment offers numerous advantages in terms of efficiency, robustness, performance, reusability, modularization, and security. The integrated transaction concept allows software products to be developed in a completely different quality level.
Despite full and complete functionality, the complete footprint (code and system data) is less than 2 Mbytes if configured accordingly.
Because all Transbase® interfaces remain identical, classic Transbase®-based PC applications can easily be ported to embedded platforms without modification. Applications and data can be used unchanged on these platforms.
Single Process Architecture (SPA):
The most important and most comprehensive new feature of Transbase® V. 8.1 is the migration from a Multi Process Architecture (MPA) to a Single Process Architecture (SPA). Transbase® now runs as a Single Process called transbase.
- Now for every Clientconnection a dedicated Thread is responsible within Transbase®.
- The Shared Memory specific for databases is substituted with memory within Transbase® which can be dynamically adapted.
- The former tbadmin services are produced via database admin 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
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.
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.
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® V. 7.1.2
Transbase® V. 7.1.2 (64bit) impresses with a considerable increase in performance compared to the previous version V. 6.9 thanks to the direct support of the native 64bit Architecture. 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.
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.
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.
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 Databases.
Transbase® V. 6.9
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).