jbogard / adventureworkscosmos Goto Github PK

I'm trying to follow along with the code in your presentation "Life Beyond Distributed Transactions: An Apostate's Implementation". I pulled the code down and have opened in VS 2019 but the projects are unable to load. Error message is: The project file cannot be opened by the project system, because it is missing some critical imports or the referenced SDK cannot be found.

Any idea what the issue is here? I have the following already installed.

1.1.0 [C:\Program Files\dotnet\sdk]
2.0.0 [C:\Program Files\dotnet\sdk]
2.0.2 [C:\Program Files\dotnet\sdk]
2.0.3 [C:\Program Files\dotnet\sdk]
2.1.2 [C:\Program Files\dotnet\sdk]
2.1.103 [C:\Program Files\dotnet\sdk]
2.1.200-preview-007474 [C:\Program Files\dotnet\sdk]
2.1.201 [C:\Program Files\dotnet\sdk]
2.1.202 [C:\Program Files\dotnet\sdk]
2.1.300-preview1-008174 [C:\Program Files\dotnet\sdk]
2.1.401 [C:\Program Files\dotnet\sdk]
2.1.500 [C:\Program Files\dotnet\sdk]
2.1.505 [C:\Program Files\dotnet\sdk]
2.1.509 [C:\Program Files\dotnet\sdk]
2.1.700 [C:\Program Files\dotnet\sdk]
2.1.800-preview-009696 [C:\Program Files\dotnet\sdk]
2.2.203 [C:\Program Files\dotnet\sdk]
2.2.300 [C:\Program Files\dotnet\sdk]
3.0.100 [C:\Program Files\dotnet\sdk]

@jbogard I'm hoping this is the right forum for this question? It is related to the code in this repo but do tell me if it isn't.

Some background.

I use the outbox pattern (from eshop guidance) in order to guarantee persistence of an integration event along with my domain state changes. My domain is simple (CRUD) and doesn't actually have domain events as such but I still need (in some cases) to persist the state changes and integration events to ensure downstream microservices can react to the integration events. This has been working well for me and I'm happy that if I needed to refactor for domain events then I could encapsulate all cross-aggregate state changes and their integration event persistence in the one transaction, with the obligatory publish of integration events outside of the transaction.

I've been keen on how to handle the outbox pattern in a nosql db for a while. I posted a question on the eshop repo here in this regard. I never thought to actually include the pattern within the document itself but after your blog and recent NDC videos a light-bulb went off.

Now to my question.

In the context of this repo's code and use cases and comparing previous uses of the outbox pattern, are the events that are persisted really domain events or are they integration events considering they are published/handled outside of the persistence transaction?

Hi,

I'm going through the code and wondering if all the repositories created during IUnitOfWork.Complete() are re-using the same IUnitOfWork instance; otherwise it looks like new events generated by aggregates that are handling the original event will not be dispatched (well until the change feed gets to them).