Hybrid vs Cloud
The architecture consists of web and function apps on Azure
(Sydney), on-premise BizTalk and RabbitMQ-based services (Hobart),
RabbitMQ hosted on CloudAMQP (Sydney), and a Postgres database on Neon
Cloud (Sydney).
For more on the architecture and what to expect in this demonstration go to
Overview. For more on BRE database facts that this demonstration uses go to
BizTalk.
| Buyer | Bid | Item | Supplier | Sid | Seconds |
| Starbucks | | | Ford | | |
Note: Endpoints are enabled on demand to avoid running always-on listeners.
| Buyer | Bid | Item | Supplier | Sid | Seconds |
| Starbucks | | | Ford | | |
| Buyer | Bid | Item | Supplier | Sid | Seconds |
| Starbucks | | | Ford | | |
Click each button and expect to see the company ID (1) for Starbucks, company ID (2) for Ford and the time it takes to process.
Note that cold starts affect the initial request for both BizTalk orchestrations and Azure Functions (consumption plan). The nServiceBus service maintains a persistent connection to RabbitMQ, avoiding this delay.