appccelerate.github.com/scopingeventbroker.html at master · appccelerate/appccelerate.github.com · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
---
layout: documentation
title: Scoping Event Broker
teaser: Appccelerate your asynchronous events by scoping it
navigation:
   - name: Overview
     link: scopingeventbroker.html
   - name: Tutorial
     link: scopingeventbrokertutorial.html
   - name: Unit Of Work
     link: scopingeventbrokerunitofwork.html
   - name: Transaction Scope
     link: scopingeventbrokertransactionscope.html
   - name: Restrictions
     link: scopingeventbrokerrestrictions.html
---
<h1>Scoping Event Broker</h1>e
<a href="https://www.nuget.org/packages/Appccelerate.ScopingEventBroker/">
    <img src="http://img.shields.io/nuget/v/Appccelerate.ScopingEventBroker.svg" title="latest version" />
    <img src="http://img.shields.io/nuget/dt/Appccelerate.ScopingEventBroker.svg" title="number of downloads" />
</a>
<a href="https://www.myget.org/gallery/appccelerate">
    <img src="https://img.shields.io/myget/appccelerate/v/Appccelerate.ScopingEventBroker.svg" title="latest alpha version" />
</a>
<a href="https://github.com/appccelerate/scopingeventbroker/issues">
    <img src="https://img.shields.io/github/issues/appccelerate/ScopingEventBroker.svg" title="open issues" />
</a>

<h2>Motivation</h2>
<p>You need to fire event broker events while saving some data into a database or another transactional system? You might be tempted to think that is a no-brainer. But consider this question: What happens when i.ex. a concurrency conflict occurs and the database transactions is rolled back? Normally your events would already be fired on the event broker. The scoping event broker handles does kind of scenarios and makes your event broker instances aware of transactions for asynchronous events. Therefore if you rollback your database, the events will never be fired!</p>
<h2>Features</h2>
<ul class="check dotted">
	<li>Rollback events with a few lines of code.</li>
	<li>Provides own unit of work to commit or rollback events.</li>
	<li>Own unit of work supports per call or per thread scoping.</li>
	<li>Supports TransactionScope including nested and dependent scope.</li>
</ul>
<p>For basic usage please see <a href="eventbroker.html">Event Broker</a> and <a href= "eventbrokertutorial.html">Event Broker Tutorial</a>
</p>