New Oscar architecture proposal

A while ago we discussed this with the @django-oscar/core team and finally I got to write it down as a proposal.

Since more and more projects implement only API and do not require frontend and/or dashboard, I came up with the raw idea of splitting Oscar into the parts, which would ease it customization:

• oscar-core - the main core functionality;
• oscar-storefront - basically all storefront views and templates;
• oscar-dashboard - all dashboard functionality.

On my latest projects we don’t use storefront or dashboard at all (basically only core functionality and API), so in this case it won’t need to disable almost all views.

Any feedback appreciated.

Please thumbs up or down if you support or down support the change.

[sasha0]

As for GraphQL: sounds like something that might go into oscar-api

Or perhaps, oscar-graphql.

[solarissmoke]

As far as decoupling components goes, the two things I would like to start with are CheckoutSessionMixin and OrderPlacementMixin.

Both of these implement a huge amount of business logic in the views, which is extremely problematic for anyone that wants to use that logic outside of a view context. I think most projects end up basically reimplementing this logic.

I’d like to move the business logic currently living in those views into separate code that doesn’t rely on a request/view context. This will also mean that things like sending order confirmation emails are not tied to views.

More generally I think we need to go through all the views and identify where there is business logic taking place that should be separated out.