SubSonic vs. ActiveRecord Lock

For the upcoming project, C # code should be written around an outdated Oracle database. It will be very data-oriented, since most of the code will process the data - there are practically no business rules. Therefore, I decided to abandon the completely fragmented ORM and chose the approach with active recording.

I come across two options: SubSonic and ActiveRecord Lock

Who has experience with both implementations? What factors should be considered when I choose between them? Which one is more stable / faster / easier to work with / has a good support community?

I would be very happy to receive a decision guide.

+3
source share
1 answer

Both SubSonic and NHibernate (which Castle ActiveRecord is built on) are full-sized ORMs.

NHibernate is generally more mature and more functional than SubSonic. It has a larger community of users and developers.

Subsonic has a faster rise time.

See also (note that reading will no longer necessarily make your decision easier, it can actually do the opposite):

Learn SubSonic before NHibernate or vice versa?

Subsonic Vs NHibernate

http://ayende.com/Blog/archive/2007/06/03/On-SubSonic-amp-NHibernate.aspx

http://subsonicproject.com/docs/Comparisons

Please note that for some names you will see: Ayende Rahien is a contributor to NHibernate, and Rob Conery is a contributor to SubSonic.

NHibernate - "" , , , , . , SubSonic, NHibernate ( ).

.

+7

Source: https://habr.com/ru/post/1718499/


All Articles