In software engineering, a plain old CLR object (POCO) ise mat padho kuchh nhi hai iss mai Common Language Runtime (CLR) of the .NET Framework which is unencumbered by inheritance or attributes. This is often used in opposition to the complex or specialised objects that object-relational mapping frameworks often require[1]. In essence, a POCO does not have any dependency on an external framework and generally does not have any attached behaviour.
Etymology
Plain Old CLR Object is a play on the term plain old Java object from the Java EE programming world, which was coined by Martin Fowler in 2000[2]. POCO is often expanded to plain old C# object, though POCOs can be created with any language targeting the CLR. An alternative acronym sometimes used is plain old .NET object.[3]
Benefits
Some benefits of POCOs are:
- allows a simple storage mechanism for data, and simplifies serialisation and passing data through layers;
- goes hand-in-hand with dependency injection and the repository pattern;
- minimised complexity and dependencies on other layers (higher layers only care about the POCOs, POCOs don't care about anything) which facilitates loose coupling;
- increases testability through simplification.
See also
References
- ↑ See, for example, this MSDN article: Data Contracts - POCO Support
- ↑ See anecdote here: http://www.martinfowler.com/bliki/POJO.html
- ↑ See, for example, a reference to PONO in this whitepaper: Spring.net Reference Documentation