Skip to content

Persistence Ignorance (PI)

Mehmet Özkaya edited this page Mar 27, 2019 · 2 revisions

Persistence Ignorance (PI) principle maintains that in a software application classes that model the field of work should not be affected by how they are persisted. Therefore, their design should reflect as closely as possible the ideal design required to solve the operational problem and should not be emphasized as to how the status of the objects are recorded and then taken. Some common Persistence Ignorance violations include domain objects that need to inherit from a given base class or must show specific properties. Sometimes insight information takes the form of properties that must be applied to the class, or it only supports certain collection types or property visibility levels. There are perspectives of ignorance, the oldest CLR Objects (POCOs) in .NET.

Clone this wiki locally