testcontainers-dotnet VS EFCore.BulkExtensions

Testcontainers

Like others said, it's better to test with an actual database. I recommend using Testcontainers (https://dotnet.testcontainers.org), you can even create multiple instances so your tests can run in parallel independently.

To launch a container in code we will use Testcontainers. Testcontainers is a library that is built on top of the .NET Docker remote API and provides a lightweight implementation to support your test environment in all circumstances. This library supports pre-defined packages for containers or you can use your .dockerfile. We will use a pre-defined package for LocalStak. LocalStack is a cloud service emulator that runs in a single container for AWS service. LocalStack supports a growing number of AWS services.

Bogus - For creating fake data Verify - Snapshot testing for .NET MELT - For testing ILogger usage Stryker - Mutation Testing for .NET TestContainers - run docker programmatically in integration tests

.NET Shop using SQL Server here, but I think something similar to what we do can apply to any stack. We use TestContainers [1] to spin up a container with SQL Server engine running on it. Then use FluentMigrator [2] to provision tables and test data to run XUnit integration tests against. This has worked remarkably well.

[1] https://dotnet.testcontainers.org/

EF Core Bulk Extensions has helped me out many a day.

I have used this and found it to have everything I need. It has a dual license though but if it is for personal use you dont have to worry about that. https://github.com/borisdj/EFCore.BulkExtensions

EF Core works for me and inserting/updating several thousand records at a time. I also found this nuget that works great https://github.com/borisdj/EFCore.BulkExtensions

Using EF core with migrations. Anything that we can’t do out of the box, we can normally do with the bulk extensions (https://github.com/borisdj/EFCore.BulkExtensions). There were two specific places I had to drop back to raw SQL, one was for a specific SELECT query that needed to be optimised, the second was a stored proc doing a MERGE that we pass in a table type (upsert of 100k records)

There is however a free nuget for EF Core which supports OP's needs https://github.com/borisdj/EFCore.BulkExtensions

For EFCore v6, you're best using EFCore.BulkExtensions, to do something like this:

I've been using this library with great success: EFCore.BulkExtensions

2nd option as you're basically doing batch save changes where batch size is 100. You should put a transaction on top of all of this though and commit at the end for data integrity reasons but that's about it. Alternatively use a NuGet that can do batch save changes (Z.EntotyFramework is paid, but https://github.com/borisdj/EFCore.BulkExtensions is free).