Why Mapping Code Generation with Orasis Mapping Studio?

There is no reason to abandon ADO.Net and the power of SQL with some ORM framework that can impact development time and performance.  There is no reason to abandon control of your data access layer to some framework and treat it as a black box and only wish that it will perform and is not easily tuned. Other factors to be considered are:

  1. The cost associated with the steep learning curve.
  2. The difficulty to find resources that can set up the entities and write code in these object Query languages.
  3. Introduction of distributed caches in an enterprise system.

Visual Mapping studio 2009 takes all of the hurdles away from the developer and targets pure performance and manageability. It isolates database access in its own tier by managing auto generated data services that concentrate on data business requirements.

  1. Enhance your investment in class libraries that currenly implement your data relationships - map directly into your existing .Net classes.
  2. Perform true (N) level nested mappings into existing classes.

Code is build to target business requirements directly:

A simple definition of a use case is to describe how to achieve a goal or task. Use cases are often associated with data requirements that reside in some database schema. A data architect (DBA) is primarily responsible for data storage and a business analyst knows the business rules that generate/operate on the data. A [Mapping] or a group of Mappings can target a business use case and through the [Mapping] Orasis Mapping Studio builds optimal and maintainable data access code that achieves the use case’s goal. Data architects and developers can target business use cases through a tool that allows both of them to optimize data access performance as well as isolation of database tier code.

 

Efficient, manageable, non-propriety code is generated:
The Code Mapping generation engine, advices the field mappings that the IDE generates in open XML format based on RDBMS and .Net object graphs metadata. These mappings allow for extremely efficient ADO.Net code generation that targets .Net runtime conversions, Nullable fields and optimal data access design patterns. It focuses strictly on data access and does not allow introduction of business layer code. The generated code has no framework dependencies with no “using statements” from ant 3rd party vendor libraries. Open source and open project format was the main goal and promise of Orasis Software , as other companies bind data access code with their own framework libraries. By simply editing any aspect of a [Mapping] through the powerful Visual Mapping Studio editors, changes can be regenerated and recompiled with a click of a button.
Code is open and can be called and extended as necessary:
The generated code can be adapted in any Visual Studio 2005 and 2008 project. Visual Mapping Studio auto generates the solution files. The generated code files can be extended and the virtual methods can be overridden as necessary. The classes are created partial as well, to make addition of any extra methods a breeze.

 

Get only the data you need and where you need it.
Orasis focuses on executing data business requirements that target data use cases. Orasis Software does not generate all sorts of classes with attributes and properties and bind your data model classes to a framework either. The data tier data models ( data contracts) are 100% free of any framework or restrictions and can be either auto generated in a different library or simply imported and mapped to any nested class level graphically ( True N level Mapping of Object Graphs ). No need to attach attributes or write XML mapping code, simply drag and drop and expand nested object graphs as necessary.

 

Code is free from configuration attributes, reflection, introspection, and third party dependencies:
Simply, operate a configuration free code generation engine, with an IDE that targets straight clean .Net code generation free of reflection and introspection in your data models (Data contracts) for population and retrieval of data. Execute raw, fast SQL without writing it and maintaining it. No need to code in some object query language that creates SQL that in many cases is not optimized at all. Be able to simply optimize performance by allowing data architects to intervene and optimize SQL without breaking your code.

 

Leverages the most efficient pattern for performing data access:
[Mapping] Code is created in data access methods that belong to data service classes. The interface of the data tier becomes the Data access service classes that utilize database connection pooling, efficient object oriented data access patterns and pure ADO.Net code.