NHibernate performance when using internet banking
We currently have a project to implement an internet banking site and are evaluating it with Nhibernate. ¿Is NHibernate suitable for this type of application where performance is important and a large number of users will be running concurrently?
¿Do you know of any successful stories of using NHibernate in such an environment?
I think NHibernate is only slow when used incorrectly, and I think we can use it with a lot of customization, best practice, and common sense.
UPDATE: We recently contacted the project and we are still collecting requirements to define the specifications. This application is for small and medium banks in our country, so they expect about 200-300 users at a time.
I'm pretty sure the DB will be in SQL Server 2005 and will be an n-tier application that uses web services to access the data layer.
source to share
My team has been using NHibernate on a high bandwidth system for years with no problem. NH is effective enough to start with and provides fine-grained control over when and how objects are recovered.
With that said, we do not know the specifics of your problem, so we cannot make certain predictions. Perform scaling tests before taking action.
source to share