What is a real -time database?

The

real -time database in some respects is similar to a traditional database. Both have aimed to keep the data and both must make calculations, but the speed at which the calculations must be completed and the amount of calculations differs significantly. The purpose of the real -time database is to make real -time calculations and is not created so that the information is kept for a long time. Real time databases include many other database size limitations and the size of the calculations-and many other considerations and factors-to ensure that the calculations are performed at a specified time. Usually there are different times of the term, so the database can prefer functions. On the contrary, the database is in real time. The data is largely kunna, with very small remaining constant and the database must be able to handle a very large number of calculations. This means that the traditional database will not work for real -time application, because the design is completely different.

Maybe the best example of a real -time database is the stock databasemarket. This database must be able to constantly change their values ​​on the basis of a large number of factors and must remain accurate for business and investors to prosper transactions. Other examples of real -time database include air control database, medical database and scientific analysis database.

When a traditional database is designed, the programmer creates a frame where information can be saved and programmed a relatively small number of restrictions. The real -time databases must have a very large number of restrictions to limit the amount of information it holds and the amount of transactions they can do so, so the CAN calculations to be performed quickly. This is because the speed of the database depends on the amount of data held and the number of functions working simultaneously. Most real -time databases are idiosyncratic or cannot be integrated into other databases because they are highly specialized in one topic.

to meet the timeExcluding or calculating the time -based calculation, three levels of priorities are located on the functions: hard, firm and soft. This goes from the fastest to the slowest, so the database knows what to work on now and what to expect. While all functions can be placed on hard priority, this can cause a large real -time database to disappear due to overload.