Performance — the jumping problem — too many database (or something else) calls

This repository holds a proof of concept in order to show how bad too many database calls are.

Tools

• Visual Studio 2019;
• .NET Core 3.1 Console Application;
• Entity Framework;
• Visual Studio Profiling;
• Docker, Postgres and AdventureWorks.

Blog

It's possible to read a deeper explanation on my medium that holds a entire post showing how bad this practice is, with some numbers and the profiler itself.