I'm part of team considering replacing NHibernate with EntitySpaces, or our own custom data layer.  Here's our situation:  We provide SaaS, Software as a Service, so we have many customers, one database, one code base (or least we're getting there).  Our applications are all web-based.  Currently our business layer is built on NHibernate.  We're finding NHibernate a little clumsy, hard to use, and not well-supported.  The only good thing about NHibernate is that it supports Memcache-D.  Before we throw out ORM altogether, I'm wondering if anyone out there can attest to the scalability of EntitySpaces, if we're willing to write stored procedures when necessary.

I read another post saying you don't support caching, and don't plan to add it, so how do we scale to 10,000 concurrent users, maybe more?

Not looking for black and white, just shades of grey...

Dave

I certainly wouldn't scratch ORM. I think the best thing to do is create a little ES test app and compare the times with your NHibernate application. I recall some posts on our forums about folks doing some very high end web sites with ES, it is very effiecient. There is this POST as well from one of our users.

 

---

EntitySpaces | Twitter | BLOG | Please honor our Software License

I read the post, and the numbers are plausible.  NHibernate is a little fat, IMHO.  However, the problem we have is under load (heavy load), where database contention becomes a problem.  A single machine test doesn't tell me enough.

Does EntitySpaces use Enterprise Library, by chance?  If so, something called NCache might be our way out...  http://www.alachisoft.com/main_index.html

No, EntitySpaces uses nothing but pure ADO.NET. However, we open and close connections correctly so it relies on .NET connection pooling and ES itself is very light on the CPU.

---

EntitySpaces | Twitter | BLOG | Please honor our Software License

Here is a post with some performance information in it.

---

EntitySpaces | Twitter | BLOG | Please honor our Software License