The Value Proposition for the Full Use of a Database for Digital Media

Database for Digital Media handling and accessHaving a single infrastructure for both digital media indexes and digital media content means having one set of management tools to deal with. In a binary system, the data must be managed separately. The media index as well as the content must be managed. For example, the content is backed up using one tool and the index is backed up separately.

Along with unifying management of the digital media database, the database has access to the set of features offered by the database. These data­base features include features for performance, security, integrity, and loss prevention of the data.

Performance features include many techniques to automatically distrib­ute the physical input/output (I/O) load among a set of physical disks. This can be very important for a media database since the amount of data that is moved from disk to the application can be large. Database indexes are well suited to finding data quickly.

A database is also especially well suited to securing data. Access can be blocked to only the users who have the privilege to access the data. This can be either on the database as a whole or individual items of media within the database itself. For integrity of the data, transactions can be used so that there is not a mismatch between what is in the index and the content in the digital media database. The database also has a plethora of techniques for loss prevention of data, from mirroring data to backing up data to real-time transfer of database updates to a remote site.

Database for Digital Media store and access

The Value Proposition for Using Media Types

Initially there was only one type of data that was stored in a database—the text type. Soon there were other types introduced, such as a number type and date type. These date and number types could be stored in the text type as well. However, by using different types for date and number types they can be better understood and better managed. For example, a number or a date could be converted to binary for efficient storage. Also, these types suggest operations that can be performed on them. For example, numbers can have arithmetic operations and dates can be output in differ­ent national standards.

The types also have the advantage that database tools and applications implicitly know how to deal with the data—how it can be represented, how it can be output, how it can be used, etc. For example, a simple image browsing application could be written to scan all the tables that belong to a user. Using the table metadata, the application can determine the tables that have an image stored in one of the columns because the table metadata indicates the column is an image type. The application can then use the image metadata stored in the image type to display the image (MIME type, width, height, etc.).

In initial unified media databases, image content was stored in simple binary large objects (BLOB) data types. These data types could be used to store any kind of data, including text, but were traditionally used for binary data items, such as every media type or large binary documents. The BLOB does not suggest what it holds and what metadata can be associated with it.

By using a type to store media data, applications can deal with the type automatically. For example, it is known that media has a MIME (multipur­pose Internet mail extensions) type. The type gives a standard way to access this MIME type. Other metadata is also implicit, for example, there is a height and width for an image, so accessors are available in the type to allow access to this information as well.

As well as being able to implicitly understand what a database column holds, a media type also has operations that can be performed on that data type. For example, the image data type has methods to do things such as making a smaller version of the image (a thumbnail image). These media operations are close to the data so that the cost of data transfer from and to the database is minimized.

 

Summary

The infrastructure for handling Digital Media has evolved from storage in simple filesystems to being managed by databases. The database infrastruc­ture has likewise evolved, increasing functionality especially for managing Digital Media. The database centralizes the management of digital media, and various other technologies are provided to access the media in the data­base. Any system designed to deal with Digital Media should strongly con­sider the advantages of managing the media within a database.

 

Вас заинтересует / Intresting for you:

Types of NoSQL Databases
Types of NoSQL Databases 577 views Валерий Павлюков Wed, 13 Jun 2018, 19:12:01
Introduction to NoSQL Database...
Introduction to NoSQL Database... 477 views sepia Tue, 12 Jun 2018, 18:51:49
Why NoSQL? Advantages over rel...
Why NoSQL? Advantages over rel... 415 views Боба Tue, 30 Oct 2018, 11:16:53
The Evolution of Digital Media...
The Evolution of Digital Media... 1053 views Akmaral Sat, 03 Feb 2018, 16:47:36