Code First or Database First

Question

Which option is better in terms of performance and flexibility?

Answer 1

Sorry, cognitive dissonance there between the subject line and the description. Could you please clarify your question?

Answer 2

thanks Janning

Answer 3

Happy to help. 🙂

Answer 4

Its not difficult to learn both at a time, take younger decision

Answer 5

what is the better option for entity framework: Code-First or Database-First for performance and flexibility?

Answer 6

Not sure if that adds much clarity, but I will try to provide some sort of opinion...

You might be referring to this:

https://www.c-sharpcorner.com/blogs/entity-framework-code-first-vs-database-first-approach

or this:

https://stackoverflow.com/questions/5446316/code-first-vs-model-database-first

of which I think the latter provides more insight than the former.

Since I would imagine most of us on this platform are (or aspire to be) programmers, we would ultimately be biased toward Code First.

In a more broad sense than just C#-MySQL specific issues, most often limitations come in the form of vendors. If they keep changing things, this becomes a moving target. The code must be nimble enough to adapt to these scenarios. Database-first can feel like having the tail wag the dog. On the other hand, it would be silly to ignore festering database issues like a black box if you can do something about them -- the state of the tail is one of the main indicators of how the dog is feeling (sad/excited/healthy).