Build with an Azure free account. Get USD200 credit for 30 days and 12 months of free services.

Start free today

The Architecture behind the nopCommerce eCommerce Platform

Play The Architecture behind the nopCommerce eCommerce Platform
Sign in to queue

Description

nopCommerce is a mature eCommerce platform build on ASP.NET Core. Originally, it was built on Web Forms and over the years it moved to Mvc and now too ASP.NET Core.

In this episode, John Baluka joins Christos to give us an interesting look at the architecture of nopCommerce. They dive into topics such as validation, dependency injection, object mapping, data access and much more.

  • [00:37] - What is nopCommerce?
  • [04:05] - What's nopCommerce built on?
  • [07:12] - Exploring the architecture
  • [15:19] - Preparing for .NET Core
  • [18:00] - Exploring the business logic components
  • [26:25] - Data access with Entity Framework Core
  • [35:30] - Reviewing the Plugins and themes

 

Useful Links

 

Embed

Download

The Discussion

  • User profile image
    keyranjoshi
    Thank you so much for this video. It's well explained and lots of learning. If you have more video about architecture and best practices please share.
  • User profile image
    johnjtheise​n11
    awesome presentation on how all the pieces can be put together for a LOB application, thanks for presenting it
  • User profile image
    jovancoleman

    I would check also GrandNode - it's a fork made from nopCommerce. It's based on .Net Core and MongoDB, but as I saw on GitHub, one of users tries to provide a support for CosmosDB for that e-commerce platform also. I will leave a GitHub link here, maybe somebody will have time to check it. - https://github.com/grandnode/grandnode

    JC

  • User profile image
    atulrungta
    Very good presentation John. Kudos to you :)

    NopCommerce really have an excellent architecture and very beautifully designed solution. They have followed OOPS concept so well that any .net developer can use nopCommerce solution to learn from it. Moreover, almost everything you want to develop is inside solution itself. If you re-use existing classes and functions, you hardly need to write a lot of code to add / extend a feature inside nopCommerce.

    Me and my team members really love working on nopCommerce :) Thank's again John for this presentation..

    Best Regard's,
    Atul
  • User profile image
    Damen

    Thank you for the great information presented.

    I'm just wondering, will nopCommerce adopt mediator & CQRS pattern. The way I see the current repository pattern being used on top of EF core, seems a little redundant, as EF Core is implemented as a repository pattern and UOW.

    Would it make sense to adopt CQRS for nopCommerce ?


    Regards,
    Damen

Add Your 2 Cents