Identity map pattern

This article relies largely or entirely on a single source . Relevant discussion may be found on the talk page. Please help improve this article by introducing citations to additional sources.
Find sources: "Identity map pattern" – news · newspapers · books · scholar · JSTOR (April 2020)

In the design of DBMS, 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 4 types of identity maps

Explicit
Generic
Session
Class

References

[edit ]

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

v
t
e

Software design patterns

Gang of Four
patterns

Creational	Abstract factory Builder Factory method Prototype Singleton
Structural	Adapter Bridge Composite Composition over inheritance Decorator Facade Flyweight Proxy
Behavioral	Chain of responsibility Command Interpreter Iterator Mediator Memento Observer State Strategy Template method Visitor

Concurrency
patterns

Architectural
patterns

Other
patterns

Books

People

Communities

See also

References