DevStory | Review workings of UnitOfWork pattern

[AnnaSasDev]

The Who - What - Why

As the Developer of InfiniLore
I want to change the UOW pattern to work with an attach - detach system towards repositories
So that we can have mulitple parallel unit of works per API connection

Additional Context

Currently one API connection means one unitofwork for the entire scope of the connection, which is "fine" but has some caviates. Currently if we wanted to have a MediatR Handler which does stuff in parallel to the db, this isn't possible, because one connection has only one DbContext. Concurrency "solves" this issue somewhat, but will still cause some roadblocks in the longrun.

Idea (pseudo):

class UnitOfWork(DbContextFacory fatory) {
    public void Attach(IRepo repo){}
    public void Detach(IRepo repo){}
}

and

class SomeRepo : IRepo {
    public static SomeRepo AsOneUnitOfWork() // Creates a unit of work through the dependency pipeline. maybe as a keyed service? Will have to think about this one further along
}

Dev-Side Criteria

No response

Ducky Acknowledgment

• I accept that this issue might be delayed or reprioritized.