DBA-Cache

Cache-per-Day

In this picture you might note the data flow, which goes from remote databases through DB-Adapters, Middleware, Frontend until it finally displays in the web browser. During this route, several levels of buffers or cache memories appear. The first important cache can be found already on the side of DB-Adapter. Each has a so-called Daily cache which contains a snapshot of a distant database in the normalized form of a set of OASIS attributes. The data in this cache are being renewed in constant intervals e.g. once a day.

Search enquiries are being executed above this normalized database especially for efficiency reasons. This is enabled by standard techniques of relational databases – indexing. The content of a database changes only when the data is renewed from a distant database, and therefore it is not a problem to rebuild all indexes. Usually, building of indexes is a time consuming activity.

Let us remark that this first level cache can be found on the side of DB-Adapter, which itself might be placed in the domain of a particular distant database. This is why there are no problems with copyrights or inconsistency between the original storage and cache at this level. The one who is responsible for everyday restoration is the provider of the particular database.

→ back to the database adapter

→ back to the Middleware

→ back to the Platform