I often get coy when I hear comparisons with Stack Overflow, Twitter, Facebook,
Blog Engines, etc. though.
Most of those platforms are happy to just throw away transactions when the
going gets heavy.
Dr Greg Low
1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 fax
SQL Down Under | Web: www.sqldownunder.com<http://www.sqldownunder.com/> |
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Craig van Nieuwkerk
Sent: Tuesday, 20 September 2016 1:33 PM
To: ozDotNet <firstname.lastname@example.org>
Subject: Re: Entity Framework - the lay of the land
To give more info, 99% of the CUD was done via NHibernate. For simple select
queries like for lookup lists was also done via NHibernate, using the built in
caching and Redis cache, but more complicated queries were straight SQL and
On Tue, Sep 20, 2016 at 1:30 PM, Craig van Nieuwkerk
Not EF but have used NHibernate in application, in conjunction with optimised
SQL where required, and easily supported 1000+ users. But it is very easy to
stuff it up and find you can't support 5 simultaneous users.
Even StackOverflow before it used Dapper used LinqToSql. Of course, they had to
optimise and go to Dapper but the LinqToSql version still supported heaps of
On Tue, Sep 20, 2016 at 1:22 PM, David Apelt
Thanks everyone for their contributions to my original questions. I am a
little surprised about how poor people’s real world experience has been with
the EF and other ORMs.
A little poll;
Is anyone successfully using EF in a production environment for a non-trivial
application? And if yes, then why has yours worked where others have failed.