Skip to content
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.
/ SqlAsbBridge Public archive

Proof-of-concept between two NServiceBus islands (ASB & SQL Server)

Notifications You must be signed in to change notification settings

lovaere/SqlAsbBridge

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
 
 
 
 
 
 

Repository files navigation

SqlAsbBridge PoC

This SqlAsbBridge project is a small proof-of-concept in order to validate the communication between two 'NServiceBus islands' with the use of the NServiceBus.Router package. With 'islands' We mean two environments with a different transport that are normally not able to communicate with each other via NServiceBus.

Azure Service Bus Island

The first island uses the Azure Service Bus transport. The SqlAsbBridge.AsbPublisher console application will publish/send the following messages on startup:

  • AzureActionCompletedEvent
  • StartAzureActionCommand

And these are handled by the SqlAsbBridge.AsbHandler project. All this happens on the ASB island, except for the SqlActionCompletedEventHandler that originates from the SQL island.

SQL Server Island

The second island uses the SQL-Server transport layer. Here we have a more or less identical setup. The SqlAsbBridge.SqlPublisher console application will publish/send the following messages on startup:

  • SqlActionCompletedEvent
  • StartSqlActionCommand

And these are handled by the SqlAsbBridge.SqlHandler project. In this case this all happens on the SQL-server transport, except for the AzureActionCompletedEventHandler that originates from the Azure Service Bus island.

About

Proof-of-concept between two NServiceBus islands (ASB & SQL Server)

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages