Skip to content
Open source core .NET 4.5 and SQL Server Sannois, France
MAGELIAWebStore
Technology · architecture

The layers, without the diagram tax

The commerce engine exposes services. The console and scheduler operate it. SQL Server stores it. The client presents it.

Model

Four questions, four layers

Where the boundaries sit

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.

Read the full architecture section

Consequences

What the boundary buys you

Client choice

A .NET, PHP, Java or mobile client can consume the same commerce operations.

Independent scaling

Application tiers can be distributed as load grows.

Narrower integration

A back office system can consume a small service surface instead of reading the database.

Primary sources

Reference shelf

Standards, documentation and tools that are relevant to this topic. They open on the publisher's site.

  • .NET platform Runtime, tooling and framework documentation from Microsoft.
  • OData The open data protocol used by the WebStore services layer.
  • SQL Server Database engine documentation and editions.
  • NuGet Package distribution used by the .NET client and samples.
  • Microsoft Learn Reference material for the Microsoft development stack.
  • GitHub Source hosting and issue tracking for .NET projects.
  • OWASP Application security guidance and cheat sheets.
  • Semantic Versioning Version numbering conventions used in release notes.
  • W3C Web standards for markup, accessibility and internationalization.
  • web.dev Performance, accessibility and Core Web Vitals guidance.
Next step

Review the architecture with your team

The useful diagram is the one annotated with your identity, content, ERP and hosting decisions.