Client choice
A .NET, PHP, Java or mobile client can consume the same commerce operations.
The commerce engine exposes services. The console and scheduler operate it. SQL Server stores it. The client presents it.
Storefront: presentation, navigation, checkout experience and the client technology. It calls services.
Services: catalog queries, basket operations, order creation, inventory and configuration. WCF and OData expose them over HTTP.
Operations: the administration console and scheduler change and maintain commerce data.
Record: SQL Server holds the relational model that all three rely on.
A .NET, PHP, Java or mobile client can consume the same commerce operations.
Application tiers can be distributed as load grows.
A back office system can consume a small service surface instead of reading the database.
Standards, documentation and tools that are relevant to this topic. They open on the publisher's site.
The useful diagram is the one annotated with your identity, content, ERP and hosting decisions.