Hi Wilmer! We have got big performance improvements in these days. The latest svn version should be by far faster than the previous.
But, IMHO, you should use Linq to Sql (or better, DbLinq) only if you need a good data access layer for an object oriented architecture (and probably a domain model) We (in my previous company) have designed a web application which required responsivity with some like 10.000 access at a second (during the point hours) and we did not used neither Linq to Sql nor object orientations. We did use fully functional REST webservices (based on fastcgi) with XSLT and a lot of client side javascript (on ajax enabled browser, the behaviour changed on non ajax browser). The rdbms was postgresql. Afaik, this is the right approach when you need to support so huge load. Giacomo On Tue, Jun 23, 2009 at 4:55 AM, Wilmer Linares M <[email protected]>wrote: > > hi everyone using DBlinq in their own projects. > I just going to enter into this new topic but i have bad firts > impression about LINQ to SQL because of many forums. > > my question for all of you is: Its advisable to use this new concept > in huge web projects with an expected large number of visitors? > maybe the use of this apply only for small projects i think... > > thanks in advance > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DbLinq" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/dblinq?hl=en -~----------~----~----~----~------~----~------~--~---
