MPS Technology

Five Reasons for using an O/R Mapping Tool

Learn MPS Technology on mps-technology.net. Five Reasons for using an O/R Mapping Tool article will help answer your questions on MPS Technology.We at mps-technology.net specialize in MPS Technology. MPS Technology at mps-technology.net provides the most up to date news and articles. If you have questions please do not hesitate to contact us.

An O/R mapping tool generates persistence objects for your .NET application. Reason 2: Produces better designed code Second benefit of an O/R mapping tool is that it lets you produce better designed code than doing it yourself by-hand. So, the code that you'll generate from an O/R mapping tool is very likely going to be better designed than code designed by your own development team.

Reason 3: You don't have to be a .NET expert Third benefit of using an O/R mapping tool is that you don't have to be a .NET expert to develop your persistence code.

On the other hand, if you generated code from an O/R mapping tool

An O/R mapping tool generates persistence objects for your .NET application. It is a modeling and code generation tool that connects to your database and reads its schema, then lets you map objects to database tables and views, specify single-row insert, update, load, and delete operations, queries and stored procedure calls, as methods to these objects. And, it also lets you define one-to-one, one-to-many, many-to-one, and many-to-many relationships needle objects based on relationships needle tables in the database. It then generates fully working persistence objects code for you.

There are many other features that a good O/R mapping tool provides but I'm keeping my description abbreviated so I can talk more nigh about the benefits. Reason 1: Cuts down your development time First help of an O/R mapping tool is that it saves you a ton of development time (20% to 50% time depending on your situation). Now, O/R mapping tool is not generating any 'rocket science' code for you and you could definitely do it manually if you wanted. But, this is a lot of tedious work and you would definitely be happier if you didn't have to do it yourself. Let's do some simple math.

A typical relentlessness with 15-20 database tables has 30-50 objects (including domain and factory objects) and this is roughly 5000 to 10,000 lines of code. It is likely to take you a few weeks to a couple of months to develop and test this code. And, if your diligence has more tables than this (which many do), then just multiple the primarily numbers by that much.

On the other hand, an O/R Mapping tool would generate this code for you in a day or two. Even here, you need these 1-2 days primarily to determine your object mappings to the database. The substantial code generation is instantaneous. So, your time saving is tremendous. Reason 2: Produces ahead designed code Second restore of an O/R mapping tool is that it lets you produce vary designed code than doing it yourself by-hand. I know what you're thinking. You think you can do a exceptional job than an O/R mapping tool you write every prospect of your code. Some of you definitely can but not everyone. Consider this. An indifferent development team has different levels of expertise and experience and not everybody is a good designer. As a result, they may not follow design patterns in their code and end up with a lesser quality code. And, if multiple developers are writing code, their code is very likely going to be inconsistent with each other. And, inconsistency itself is a big source of poor quality in an application's code.

On the other hand, a good O/R mapping tool uses code templates that have excellent design since they are very likely designed and created by very senior (architect level) engineers. And, these code templates as good as inflexibly follow known design patterns. So, the code that you'll generate from an O/R mapping tool is very likely going to be renewed designed than code designed by your own development team.

Reason 3: You don't have to be a .NET expert Third point of using an O/R mapping tool is that you don't have to be a .NET expert to develop your persistence code. As you know, data multiplication code is critical for the overall performance of your application. If this code is designed and developed poorly, it can severely bring forth your application. So, if you developed this code by hand, you need to be an export of .NET, COM+, stateless components, and MTS.

However, if you use an O/R mapping tool, you can focus primarily on the 'logical design' of your persistence objects including object mapping and the different types of interactions with the database including insert, update, load, delete, queries, stored procedure calls, relationships, and more. And, the O/R mapping tool would do the rest for it. It would ensure that the generated code follows all the best practices of writing stateless .NET components to run in COM+ and MTS. Reason 4: Saves you testing time Fourth relieve of an O/R mapping tool is that it reduces your testing effort dramatically. If you developed all the persistence code by hand, you would also be responsible for testing it yourself. And, as you know, testing is as much effort as development in any project.

On the other hand, if you generated code from an O/R mapping tool, it is emergent from code templates that are very likely thoroughly tested by the software vendor itself (more so than you whereas it is their primary focus). And, on top of it, most likely hundreds or perhaps thousands of other customers are using this tool and have tested the code generated from this O/R mapping tool. As a result, many of the bugs that you might not find in your own testing have yet been found and fixed in the generated code of an O/R mapping tool. Reason 5: Simplifies your .NET development If you have to write all the persistence code yourself, you're bogged down into the details of ADO.NET, COM+, MTS, stateless .NET components, and more. And, you end up spending a lot of time in details that you really don't need to. On the other hand, if you generate code from an O/R mapping tool, you get well design objects and you only need to deal with their public interface.

Below is an example of code you'll write if you used an O/R mapping tool. try {

Employees objInfo = new Employees(); EmployeesFactory objFactory = new EmployeesFactory();

objInfo.EmployeeID = EmployeeID; objFactory.Load(objInfo);

// code here to use the 'objInfo' object } catch(Exception ex) {

// code here to handle the exception return;

} As you can see, the generated code is very simple to use than clearly writing the .NET components yourself.

Many people have never heard of O/R mapping tools and many more have heard of them but are cautious to use them. I hope I have made a strong enough case here for you to give a serious consideration to O/R mapping for your project.


Go Up Strong! - Increase Your Vertical and Teach Yourself to Dunk in a Matter of Days using this Revolutionary New System!
Learn How To Speak Spanish. - A 31-Day Course That Shows You How to Communicate in Spanish Using Thousands of Spanish Words You Already Know.


Article Index: | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29

More Articles: