none
Scalability using Entity frameowrk for large data RRS feed

  • Question

  • Hello,

    We are planning to use entity framework for interaction with SQL. There will be direct EF queries as well as EF calling SQL stored procedures. The amount of data in these transactions can be very high, e.g. 100 K records.

    Is there any analysis done on using EF with large Data transactions? also are there documentations around scalability using EF?

    Wednesday, October 29, 2014 8:52 PM

Answers

  • We are planning to use entity framework for interaction with SQL. There will be direct EF queries as well as EF calling SQL stored procedures. The amount of data in these transactions can be very high, e.g. 100 K records.

    An ORM is more suited for SOA, Web based and client/server type solutions, quick hitter type solutions you get in and you get out, and the lifetime of this is short.

    Is there any analysis done on using EF with large Data transactions? also are there documentations around scalability using EF?

    An ORM shouldn't be used for long running jobs pushing large amounts of data. The fact that you are using an ORM encapsulates scalability, because of OOP.

    http://www.ozedweb.com/infotech/it_oops_lesson30_scalability.htm

    The use of sprocs is questionable, because the sprocs had better be geared towards doing simple CRUD operations for an object/table for usage with EF. Otherwise, you got trouble trying to use existing sprocs that have nothing to do with EF and EF functionality.

    Thursday, October 30, 2014 4:27 AM

All replies

  • It's always expensive to move data. Are you primarily loading data, returning data to the client, or manipulating data on the server?

    David


    David http://blogs.msdn.com/b/dbrowne/

    Wednesday, October 29, 2014 9:37 PM
  • We are planning to use entity framework for interaction with SQL. There will be direct EF queries as well as EF calling SQL stored procedures. The amount of data in these transactions can be very high, e.g. 100 K records.

    An ORM is more suited for SOA, Web based and client/server type solutions, quick hitter type solutions you get in and you get out, and the lifetime of this is short.

    Is there any analysis done on using EF with large Data transactions? also are there documentations around scalability using EF?

    An ORM shouldn't be used for long running jobs pushing large amounts of data. The fact that you are using an ORM encapsulates scalability, because of OOP.

    http://www.ozedweb.com/infotech/it_oops_lesson30_scalability.htm

    The use of sprocs is questionable, because the sprocs had better be geared towards doing simple CRUD operations for an object/table for usage with EF. Otherwise, you got trouble trying to use existing sprocs that have nothing to do with EF and EF functionality.

    Thursday, October 30, 2014 4:27 AM