Embedded database system

from Wikipedia, the free encyclopedia

An embedded database system is one in a software application embedded database system that does not visibly appear to the outside.

properties

Some database system manufacturers sell their database products not only as stand-alone products, but also as embedded database systems that are integrated into other applications.

An embedded database system cannot be recognized as such from the outside and cannot be used by third-party systems for data storage either. The advantages of embedded database systems result from the fact that the manufacturer can carry out an adaptation geared towards the specific application that goes beyond the possibilities of normal administration and acceleration.

Another benefit is easier installation and licensing of a product that uses an embedded database system. The product manufacturer can deliver his product as a whole to his customers. Licenses for his product can be negotiated between the product manufacturer and his customer without the involvement of the database manufacturer. The product manufacturer can reach a license agreement with the database manufacturer without the involvement of his customers. One disadvantage, for example, is that it is more difficult to transfer the data saved in this way to a system from another manufacturer.

The embedded database market size was estimated at $ 2 billion in 2005 with an increase to $ 3.2 billion in 2009.

The term embedded database system is broad and includes:

Use in small and very small devices

Many database systems (DBS) are subject to the requirement to be able to manage ever larger amounts of data and to provide ever more extensive functions. But there is also a growing need for small DBSs for embedded systems and for mobile devices with poor computing power.

The design goal of such DBS is to provide a certain performance in a resource-constrained environment.

The required performance often does not consist of the full SQL3 functionality, but includes it

If a DBS is configured for use in a resource-constrained environment, it is possible that components that are considered to be essential characteristics of a DBS are left out.

Examples:

In these cases, it is no longer an "embedded database system ", but an "embedded file system ".

An example of an embedded file system is Prevayler .

List of embedded database systems

List of client-server databases that are suitable for use as an embedded database system:

List of databases that can be embedded directly in other applications:

See also

literature

Web links

Individual evidence

  1. Oracle® Buys Open Source Software Company Sleepycat. In: oracle.com. February 14, 2006, accessed March 28, 2018 .
  2. IBM DB2 LUW V9 Administration Guide Implementation Chapter 1. Here you can find information on how to handle multiple DB2 installations with the same or different versions. It explains what to watch out for when using it in embedded systems.
  3. Axion Development Team: Axion: Java Database Engine. Accessed March 28, 2018 (English).
  4. Daffodil-DB-Open-Source ( Memento of the original from October 10, 2007 in the Internet Archive ) Info: The archive link was inserted automatically and has not yet been checked. Please check the original and archive link according to the instructions and then remove this notice.  @1@ 2Template: Webachiv / IABot / db.daffodilsw.com
  5. quadcap.com ( Memento of the original from August 18, 2007 in the Internet Archive ) Info: The archive link was inserted automatically and has not yet been checked. Please check the original and archive link according to the instructions and then remove this notice.  @1@ 2Template: Webachiv / IABot / www.quadcap.com
  6. raima.com
  7. smallsql.de
  8. transaction.de
  9. dataweb TurboDB