Painful lessons learned from the Entity Framework

 

Personal rating:

After six months of development, the project has been operated. but in retrospect, there were a lot of problems encountered throughout the project, but fortunately Demand Planning has been very good (the reason is that the boss was originally a product director and the current planning is very logical ), therefore, developers do not suffer. the problem is that Microsoft's Entity Framework EF is so annoying (Personal ignorance) that we have wasted a lot of time.

1. Efficiency (if I want to share the same feelings with anyone who has tested it, it is nowhere to be seen as inefficient In addition, deletion, modification, and query, I would like to say that if you want to execute the original SQL expression or the second-level LINQ statement, it will not be necessary at all. What's more, LINQ is a controversial technology, once someone tests his efficiency, they will know.

The efficiency of a single physical framework is extremely high in a project with a concurrency performance of tens of thousands)

Second: data redundancy (if you query one or two fields, your query results are really terrible... not to mention)

Third: Project version Update (If your project version is updated, You need to regenerate the database (modefirst). What do you need to do? Think about it)

Of course, it also has a bit: But we can replace it with powerdesigner.

 

Lesson: simple implementations may use other things for Exchange (performance). The latest is not necessarily the best.