EF Core supports two main approaches, Code First and Database First. They differ in which side defines the model, your C# classes or an existing database.
With Code First, you write the entity classes and a DbContext first. Migrations then create the database and change its schema as the classes change. This suits new projects where the team has full control over the data model.
With Database First, you start from an existing database. The Scaffold-DbContext command, or dotnet ef dbcontext scaffold on the CLI, generates the DbContext and entity classes from its tables. This suits existing databases and database-driven development, where the schema is designed first.
Model First belongs to EF6, not EF Core. EF Core has no visual designer and no EDMX model file, so you model in code or start from the database.
This answer doesn't lend itself to a diagram - it reads best . No credits were charged.
Why there's no diagram: “”
The interactive diagram is below the answer - jump to diagram ↓ · Below it, the related concept . Jump to it ↓
The diagram below the answer is the concept . Jump to it ↓