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

A services layer on a standard .NET foundation

WebStore separates the commerce engine from the storefront. The engine exposes services, the storefront chooses the technology and SQL Server holds the record.

Technology at a glance

Magelia WebStore is built around a commerce core, a services layer, an administration console and a scheduler. The storefront is a client of the services, not the centre of the architecture.

That choice has a practical consequence: a team can build a PC storefront, a tablet interface, a mobile application or a content system integration without moving the commerce data.

.NET 4.5Runtime
WCFInteractive services
ODataQuery services
SQL ServerData

Why choose Magelia WebStore

The case for the platform is not a single feature. It is the combination of a free open source core, standard Microsoft technology, a small services surface and an extension model that does not require a permanent fork.

  • Open core: the Community Edition is licensed under OSL 3.0 and exposes the source of the core.
  • Standard stack: .NET, SQL Server, IIS and Visual Studio are familiar to most Microsoft teams.
  • Low entry cost: SQL Server Express and the Community Edition make a first installation inexpensive.
  • Replaceable presentation: the storefront can be built in the technology the team already uses.
  • Extensible edges: override the component that differs instead of copying the whole product.

Architecture

The services layer gives access to catalogs, categories, products, baskets, inventories, orders and configuration. Application tiers can be distributed across servers as load grows.

What runs where

The administration console manages the commerce model. The services layer answers storefront requests. The scheduler runs recurring work. The database holds the record, and the client applications decide how the experience is presented.

WCF handles the interactive calls, while OData supports query style access to catalog data. Both are reachable over HTTP, which is why a non .NET client can participate.

Extensibility is designed around component replacement. A tax rule, for example, can be overridden without editing the rest of the commerce engine.

Technology and technical requirements

The original product targets a Microsoft server environment. Treat the list below as a legacy baseline and confirm current support with Magelia before a new deployment.

ComponentPublished baseline
Runtime.NET Framework 4.5
Web serverIIS 7
DatabaseSQL Server Express 2008 or above
DevelopmentVisual Studio, NuGet client
ServicesWCF and OData over HTTP

Read the requirements page

Direction

The documented release history runs through version 2.3 in 2013. Themes in the later documentation included modularity, content types, scheduling and import export. Treat any statement about future availability as a question to confirm with Magelia, not as a published commitment.

See the release history

Primary sources

Technology 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 against your own estate

The integration points matter more than the diagram. Bring the identity provider, the ERP, the content system and the hosting model.