Try the Demo

This demo is best experienced by starting with the Company page, then progressing through Companies and Supplier. These pages execute live requests and show how database facts are resolved using the rules engine.

What to Expect

BizTalk Button - Hybrid Cloud Architecture (Slowest)
Sends a request through Azure WCF Relay to an on-premise BizTalk orchestration
The orchestration executes a Call Rules shape that queries database facts
Returns the result back through the relay to the web app

NServiceBus Button - Message Queue Architecture (Faster)

Sends a message to CloudAMQP (RabbitMQ in the cloud)
An on-premise Windows service listens to the queue and picks up the message
The service calls the BRE via .NET to execute the same database fact query
Returns the result through the messaging infrastructure

Function Button - Cloud Migration Path (Fastest)

Executes an Azure Function App that replicates the BRE database lookup logic
This approach addresses the limitation that BizTalk's database facts cannot run in the cloud
The function performs the equivalent database query that the BizTalk BRE policy would execute
Demonstrates a migration pattern for moving business rules to cloud-native architecture

All three buttons return the same result, executing identical business logic via distinct architectural approaches.

For background on the underlying rules-engine pattern and its evolution, see the BizTalk page.

Postgres

Postgres on Neon

Cloud Migration: Proves database facts can work outside BizTalk BRE (required for cloud migration since BizTalk database facts can't run in the cloud)

Infrastructure Cost: Neon's true usage-based pricing (compute billed only when active) and open-source Postgres (no licensing fees) reduces costs compared to Azure SQL's minimum vCore billing and license-included pricing