Jump to content

Identity map pattern

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Dgpop (talk | contribs) at 02:14, 7 April 2020 (cleanup template; removed See Also to prominent link; numbers instead of bullets). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

In the design of database management systems, the identity map pattern is a database access design pattern used to improve performance by providing a context-specific, in-memory cache to prevent duplicate retrieval of the same object data from the database.[1]

If the requested data has already been loaded from the database, the identity map returns the same instance of the already instantiated object, but if it has not been loaded yet, it loads it and stores the new object in the map. In this way, it follows a similar principle to lazy loading.

There are four types of Identity Map

  1. Explicit
  2. Generic
  3. Session
  4. Class

See also

References

  1. ^ Fowler, Martin (2003). Patterns of Enterprise Application Architecture. Addison-Wesley. pp. 195–199. ISBN 0-321-12742-0.