Hi abdu bukres,
Poco has some positive things like independence but also has negative effects like lazy loading and change tracking are not working well, reflection has to be used to read and write data, what is slow.
The OpenAccess approach is to make backend dependent class definitions necessary where you are close to the server and performance counts. As soon as you need poco, for data transport or n-tier applications we provide a generated poco model for you to fulfill your needs. If you are scared about the independence of your layer in a fat client or applications server tier, the recommended way is to use interfaces on top of the persistent model instead of a slower poco model.
All the best,
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking
system and vote to affect the priority of the items