When will you use this?

Use EF Core when your app stores data in SQL Server, PostgreSQL, or SQLite.

• Orders, customers, and products live in SQL Server — EF Core reads and writes them with C#.
• Migrations let teams update database schema without manual SQL scripts in production.

Real-world: Power BI-style analytics API

The Analytics team building Power BI-style analytics API uses EF Core Performance to avoid loading 10,000 products when the page shows 20. business analysts never see the C# code — they just get a fast, reliable KPI reports and filtered data export.

Production-style code

public class ShopDbContext : DbContext
{
    public ShopDbContext(DbContextOptions<ShopDbContext> options) : base(options) { }
    // DbSet properties for EF Core Performance
}

What happens in production: In Power BI-style analytics API, getting EF Core Performance right means business analysts trust the KPI reports and filtered data export every day.

Lesson example (start here)

Copy this smaller example first. Once it works, compare it with the real-world code above.

public class ShopDbContext : DbContext
{
    public ShopDbContext(DbContextOptions<ShopDbContext> options) : base(options) { }
    // DbSet properties for EF Core Performance
}

Line-by-line walkthrough

How it works (big picture)

• Study the example line by line.
• Each part connects to EF Core Performance.
• Edit one line, save, run dotnet run, and see what changes.

Do this on your computer

1. Update ShopDbContext or your entity classes.
2. Create or apply a migration if the schema changed.
3. Query or save data and verify in SSMS or Azure Data Studio.
4. Read the real-world section and name which part of the app uses this topic.
5. Run the example locally with dotnet run and confirm the same behavior.
6. Change one value in the example (route, text, or connection string) and predict what will happen before you save.

Experiments — try changing this

• Change a string or route in the example and save — watch the browser or Swagger response update.
• Break the code on purpose (remove a semicolon), read the error message, then fix it.
• Add one more property to the entity class and create a migration.
• Use dotnet watch run while editing EF Core Performance — the app restarts on save.

Remember

You learned what EF Core Performance is and when to use it in ShopNest. Practice by changing the example yourself. Use the Next link when you can explain it in your own words.

Common questions