Microsoft Bot Framework Template — Architecture

Role

The host exposes Bot Framework HTTP endpoints (Azure Bot Service / Direct Line consumers) and reuses ConnectSoft cross-cutting stacks: logging, health, optional Orleans, messaging, and observability from base-template/.

Layering

1. Base kernel — MicroserviceRegistrationBase patterns from submodule ApplicationModel projects where unforked.
2. Forked ApplicationModel — adds Microsoft Bot Builder registration (AddMicroserviceMicrosoftBotBuilder and related), Web API application parts, and Application Insights bot-specific telemetry hooks.
3. BotModel — conversation routing, dialogs, middleware, adapter configuration surface.

Boundary

Business rules that are not chat-specific still live in DomainModel / services; BotModel orchestrates conversation flow and calls application services—mirroring how other templates keep ServiceModel thin.

Related

• Base Template — Architecture
• Microsoft Bot Framework (conceptual)
• Repository docs/ and README for adapter and endpoint details.