How ORM (Relational Object Mapping) is Established in the Database World

Question

I am not a database administrator or architect, so I should ask those who do this 24/7. How established is the concept of ORM (relational object mapping) in the world of administration and database architecture? Is this still happening, widely endorsed, but still at an early stage or not at all approved? I am studying this area and want to get an idea of ​​whether this knowledge will be appreciated by a wider segment of this area.

Answer 1

Widely used and definitely the present and near future. Access to the database using manual SQL generation code was always fraught with hard work and typos, and at best was cumbersome. ORMs allow you to use persistence storage in a programmable way.

I thought this blog argued well for this: http://jonkruger.com/blog/category/fluent-nhibernate/ and SO posts like this ( nHibernate and LLBLGen Pro ) show how many people use them.

Answer 2

Many places use them, this does not mean that they use them well or that they are a good idea for the long-term health of the database. This does not mean that they are not either, usually it means that the people who choose them do not think about how this affects database design, maintenance and performance over time.

Answer 3

ORMs are widely used. Django (python web application framework) uses SQLAlchemy. Hibernate is popular for Java programs. ORMs speed up SQL application development, reduce the amount of template code you need to write, and hide which database you use from the rest of the application. Performance may suffer using ORM, so be prepared to tweak things as needed.

Answer 4

I can tell you from my experience. We are a $ 2.5 billion manufacturer of solar products, and we base our next generation of products on ORM technology. We use Linq-To-SQL, quite successfully. We are very pleased with this.

Answer 5

The concept has existed for at least 20 years.

If you look at any decent web infrastructure, whether it's Java, Ruby, PHP, C # or Python, they all include ORM. This is generally perceived as a more professional choice if you do not have specific requirements for high performance or custom SQL.