nhibernate - Does an ORM integrate with existing applications or do I not understand? -
Assume to be in Hibernation for ORM.
I am not sure how to ask this, I want to create an application that can change the share of others. For example, say, I have a "different" module, which is called the "big" app. This application can handle HR, financial, purchase, skill set, etc. But perhaps, for any reason, I do not like the skill set module, but I like the rest of the app. I want to create an app that uses the "big" app, but uses the same database, but uses that software as the front end of that piece.
I can become my app Databases do not directly with ORM My question is that there is an advantage to use an ORM here. I am thinking that if the "big" app goes away and the second app is bought, then we can continue to use the version of our skill because I am using it in hibernation instead of hitting it in a straightforward manner. I am still learning but I thought that my application used those items which I named and in this case I have just told that I have to reduce my mapping files and / and my code too much.
Here is another example. I have a legacy application and legacy database, it uses Database X. I decide that I'm not like the old terminal emulator application that is used to get data and I need a graphical version. I can use Hibernate with my application and when I finally decide to get rid of the legacy database and change to the latest Oracle or SQL Server, can I do this with very little headaches? Or is my database changing so much that it will not make any difference (I am suggesting that by changing the new database, more information should be obtained)?
I was hoping for comments, if I think incorrectly / Hibernate / ORM can be a benefit or may be.
Thank you.
I do not think you will have a big advantage that changes the database schema completely differently, You may have to make more changes than just mapping - especially if more "structure" is added to the database (tables, columns, and such schema items). It has been said that if the database was structured in much the same way, but the names of the columns and the names of the tables are changed and some tables are mixed or something similar - you get the same by changing your mapping can do.
But I would really recommend using Habeent for database diagnostics, this is a very easy way
And then just because it does not help you at all if you The entire database has changed, so it is an incredible amount of other forces, which I choose as much as possible direct access to DB.
Finally, you can think of using a service-level such as repository patterns that remove data access, so that the business of your applying will not need to change when the database changes. .
Comments
Post a Comment