Object Relational Mapping in Spring.Net

Object relation mapping is one king of method that relates real world object to data source as described by software development companies. There are certain issues to map object to data source but ORM provides three ways to deal it like bottom up, top-down and meet in the middle. Each approach has its own advantage and disadvantage. To select the best software solution, developers have to understand the environment and design requirementscompletly. 

There are certain benefits of ORM:

• Simplified development because ORM automates object-to- data table and data table-to-object conversion, resulting in lower development and maintenance costs
• Code is reduce as compare to other database like stored procedure. 
• Improve performance by keeping transparent caching in application.
• By creating optimum solution, it makes application faster.

Custom software development companies should consider following object relational mapping tools which are used in .Net

·         Base One Foundation Component Library, free or commercial

·         Castle ActiveRecord, ActiveRecord for .NET, open source

·         DatabaseObjects .NET, open source

·         DataBloks .NET, free or commercial

·         DataObjects.NET, commercial

·         Dapper, open source

·         ECO, commercial but free use for up to 12 classes

·         Entity Framework, included in .NET Framework 3.5 SP1 and above

·         EntitySpaces, was commercial, now free

·         iBATIS, free open source, maintained by ASF but now inactive.

·         LINQ to SQL, included in .NET Framework 3.5

·         LLBLGen Pro, commercial

·         Neo, open source but now inactive.

·         nHydrate, open source

·         Persistor.NET, free or commercial

·         Quick Objects, free or commercial

·         Signum Framework, open source

·         SubSonic, open source