Skip to content
Open source core .NET 4.5 and SQL Server Sannois, France
MAGELIAWebStore
For the technical team

A commerce service you can reason about

A services layer, a standard .NET stack and extension points that do not require a permanent fork.

The work

What this role needs from the platform

The same capability can be a feature, a risk or a time saver depending on who is using it.

01

Choose the storefront technology

Call the services from ASP.NET, PHP, Java or a mobile client. The commerce engine does not dictate the presentation tier.

02

Scale the layers that need it

Services, administration and the scheduler can be distributed across servers as load grows.

03

Extend a component, not the whole product

Override the behaviour that differs, keep the rest of the core intact and make upgrades a realistic plan.

04

Start from working code

The .NET client, the ASP.NET MVC sample store and the console reduce the distance from install to a working storefront.

Capabilities that support this role

Primary sources

Role 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

Bring the role to the requirements meeting

Each role should name the two tasks that cost the most time today. Those tasks are the real evaluation criteria.