I was raised in a part of web developmentland where the creation of websites is mostly synonymous with Wordpress, FTP, Joomla, and procedural code, instead of things like TDD, A/B testing, Doctrine, and design patterns. Having not traveled this area much, I'd like to know when object relational mapping and ORM tools are necessary to create and manage a site. Can you provide some generic (but real world examples) of when it should be used?
closed as too broad by gnat, MichaelT, durron597, GlenH7, Bart van Ingen Schenau Apr 3 '15 at 12:43
There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question.
ORMs are an layer of abstraction over the database. They are intended as translators between object graphs and database tables/relationships. In this capacity they simplify simple data access and with a large object model/database can save a lot of time otherwise spent writing boilerplate code for data access (getting a record by ID, deleting it by ID, updating and inserting a record).
Useful? Almost always, for the points made above.
There are no rules, as such, but ORMs are best used for basic DB operations (Insert, Update, Delete, Select). When you need something more complex, it is best to use the standard API for your platform.
ORM tools should be used for CRUD, that 80% of code that is so tedious to write over and over, that you want to bang your head against the wall.
Feel free to use more "old school" methods like Stored Procedures for the remaining 20% (e.g. operations that require performance optimization).
For a simple example of how ORMs can be effectively used to create an organized and effective Repository class for retrieving and updating database data CRUD style, see here:
ORM's serve two worthwhile goals;
Abstracting some of the database specific dialect details; and otherwise insulating developers from the weirdness that SQL can sometimes be.
Most ORM's are an 80-20 sort of tool, where they can significantly simplify about 80% of the work of persistence, compared to using SQL directly. For simple applications, 80% is really 100%, since the platform can often direct the design decisions.
Larger, more complex applications will always have problems that could not have been anticipated by any tool. The difference between good and bad ORM's shows in sharp relief when this happens.
A good ORM will get out of the way of developers when they need to issue custom SQL to get at their data, or even provide simple extension or introspection mechanisms to grow into the needed use. Poor ones just get in the way of this sort of thing; requiring developers to do these custom jobs at a lower layer.
Attaching business intelligence or other convenient behaviors to the persistent entities.
Getting the most out of the class mapping features of ORM's often requires a deep understanding on the part of the ORM's developers what role application objects play. The model objects fulfill a very different role from the persistent state they wrap.
Specifically, the rows and columns in a database represent the set of facts believed true, but the methods and inheritance graphs of the models are the rules and formulae that the application operates on.
When an ORM conflates the two ideas, they'll obstruct developers in a number of idiomatic ways. There will be no way to operate on relations that aren't part of a table (obvious counterexamples are the rows returned by a select containing joins or group by clauses). Another breakdown is that they assume that every table must have a primary key; or that the primary key must be an integer or a single column. A more subtle way ORM's can mess this up is by providing object features, like many-to-many properties, that somehow require a database connection to work properly (the entity relationship is not related to persistence).
If your application is using a relational database, your code will contain a lot of SQL (or LINQ if you are using .NET).
The ideas is to simplify interacton between application code and the database by creating Data Access Layer and business objects quickly and without coding, yet allows the developer to extend the logic by adding special business rules (if any).
Object Relational Mapping tools are many. Not all tools are the same. Some are simple whereas some are complex enough to be an entire framework.
They rely on database already built (tables) and read the table definitions from your database then:
0-Creates classes that represent objects (usually 1 to 1), such classes contain methods to read, write, update and delete data from the database. Some support LINQ (.Net) and some have their own object query language.
1-Handle primary key generation and table to table relationships automatically
2-Can read and return data related to a table automatically with one method call
3-Allow you to switch the database without coding
4-Take care of data buffering to enhance performance
5-Generate necessary SQL to get and put data to database automatically
6-Some generate web services automatically (e.g. Oxygen)
7-Some can generate auditing code for you automatically
8-Some can create stored procedures
9-Some provide authorization support
10-Some support multiple tier architecture automatically
11-Some support .NET Entity Framework
So if you need any of the above services in your project, ORM may be for you.
It may be something for you to decide whether you want to use ORM or Entity Framework if you are a .NET user.