Will the "Entity Framework integration with SQL Persistence" also include Outbox?

[Stig_Christensen]

I have read the section “Unit of work” here Entity Framework integration with SQL Persistence • Sql Persistence Samples • Particular Docs

Does the RegisterComponents also ensures that if Outbox is enabled, that this is participating in the same transaction as EF DbContext?

[mauroservienti]

Hu, @Stig_Christensen.

@Stig_Christensen

Does the RegisterComponents also ensures that if Outbox is enabled, that this is participating in the same transaction as EF DbContext?

the Outbox is not influenced by the RegisterComponents call. If the Outbox is enabled in the endpoint configuration, it’ll be used. In this case, the outbox will use (and control) the same connection and transaction that the example uses to create the Entity Framework data context instance. As shown, it’s essential your code uses the connection and transaction from the ISqlStorageSession instance.

.m

[Stig_Christensen]

Great. But is this the recommended way to integrate the Outbox pattern with EF? Instead of creating a custom EF DbContextFactory and connecting with the ISqlStorageSession as described here

RabbitMq, SqlServer, EF Core and Outbox

If you are willing to take a dependency on NSB within your EF configuration, you can use a DbContextFactory approach to set the external outbox connection and transaction. Take a look at this EF Core article: Advanced Performance Topics | Microsoft Learn The concept will be the same (paraphrasing to your use case): Register a context factory as a Singleton service: builder.Services.AddDbContextFactory<SomeDbContext>( o => o.UseSqlServer() // use this override that doesnt provide a connec…

[mauroservienti]

@Stig_Christensen

Great. But is this the recommended way to integrate the Outbox pattern with EF? Instead of creating a custom EF DbContextFactory and connecting with the ISqlStorageSession as described here

Conceptually, they are doing the same thing. The following piece of code:

COPY CODE|COPY USINGS|EDIT
endpointConfiguration.RegisterComponents(c =>
{
    c.AddScoped(b =>
    {
        var session = b.GetRequiredService<ISqlStorageSession>();
        var context = new ReceiverDataContext(session.Connection);

        //Use the same underlying ADO.NET transaction
        context.Database.UseTransaction(session.Transaction);

        //Ensure context is flushed before the transaction is committed
        session.OnSaveChanges((s, cancellationToken) => context.SaveChangesAsync(cancellationToken));

        return context;
    });
});

Is the context factory.