What does it mean that Linq To SQL does not scale?

Question

I once heard from some developers that L2S is not scalable. I'm not sure I fully understand what this means. I assume this has something to do with the layers in your application (assuming the application is layered). Can someone shed light on this topic?

Thanks Avi

Answer 1

It is rather functional scalability. If you look at the LINQ domain objects you created, you will see a lot of bloat, which may become unnecessary if you switch to another storage infrastructure such as NHibernate. One option is to deploy your own domain level, which is more abstract and maps your generated domain to abstract. Saving your domain level "without hacking" allows you to reuse it with various conservation platforms. L2S is not very good at that. Other things may include performance, but I thought it was improved in later versions?

Answer 2

, , , Qaru , .

Answer 3

Even if your collections are small, the SQL generated by the code generator will never be as optimized as manual-encoded SQL, especially if getting a good execution plan is highly dependent on choosing the right indexes.

Assuming that you manually code these cases and use SP, in cases where the data is very large, you will need many tricks to use memory efficiently, regardless of whether your database engine can help you or not.

But every abstraction has limits.