Edge Rewrite
// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a21b54e149cc3014

Jump to content

Identity map pattern

From Wikipedia, the free encyclopedia

In database design, 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

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

See also

[edit]

References

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