无需BizTalk ESB Toolkit，BizTalk能否实现支持同步队列收发的松耦合架构？

Absolutely—you don’t need the BizTalk ESB Toolkit to build a loosely coupled architecture with core BizTalk Server. The platform has native features that fully enable this, and it can handle synchronous send/receive operations with queues too. Let’s break this down clearly:

Can Core BizTalk Support Loosely Coupled Architectures? #

Yes, absolutely. BizTalk’s core design is built around decoupling systems. Here are the key native features that make this possible:

• Publish-Subscribe Messaging Model: This is the foundation of BizTalk’s loose coupling. Instead of hardcoding point-to-point connections, senders publish messages to the BizTalk Message Box, and subscribers (like orchestrations, send ports) pick up messages based on subscriptions (e.g., message type, context properties). Senders never need to know who’s receiving their messages, and you can add/remove subscribers without changing existing code.
• Adapter Abstraction: BizTalk’s wide range of adapters (MSMQ, WCF, SQL, IBM MQ, etc.) abstract away the underlying transport and protocol details. Your business logic only interacts with standard message schemas, so switching from MSMQ to IBM MQ (or any other queue/transport) doesn’t require modifying core integration logic.
• Schema-Driven Contracts: All message exchanges rely on XSD schemas, acting as a shared contract between systems. Systems only need to understand the schema, not each other’s internal implementations—this creates a clean separation between integration layers and business systems.
• Decoupled Orchestrations: Orchestrations (BizTalk’s workflow engine) can interact with the Message Box via ports and subscriptions, rather than directly calling other systems or services. You can modify orchestration logic or replace dependent systems without breaking the entire integration flow.

Handling Synchronous Send/Receive with Queues #

While queues are typically associated with asynchronous messaging, BizTalk supports synchronous request-response patterns with queue-based adapters. Here’s how to implement it:

• Use Request-Response Ports: Configure a Request-Response Port in BizTalk, binding it to a queue adapter that supports request-response (like MSMQ or IBM MQ). When you send a message through this port, BizTalk will wait for a corresponding response message before proceeding.
• Correlation for Message Matching: To ensure the response is matched to the correct request, use correlation properties. By default, BizTalk uses the MessageID of the request to correlate with the RelatesTo property of the response. You can also define custom correlation sets if you need to use other unique identifiers.
• Synchronous Orchestration Patterns: In your orchestration, use a Send shape followed immediately by a Receive shape, and link them with a correlation set. This will pause the orchestration execution until the response is received (or a timeout is hit), effectively creating a synchronous workflow over a queue.
• Timeout and Error Handling: Don’t forget to configure timeouts on your request-response ports to prevent orchestrations from hanging indefinitely. You can also add exception handling shapes to catch timeout errors or failed message deliveries and implement retry logic or fallback actions.

Quick Example Workflow #

1. Your orchestration generates a request message and sets a unique correlation ID (or uses the default MessageID).
2. The request is sent to a queue via a request-response port.
3. The orchestration waits, paused at the Receive shape, until a response with a matching RelatesTo ID arrives in the queue.
4. Once received, the orchestration processes the response and continues execution.

内容的提问来源于stack exchange，提问作者user217648