Services Concept

[pozylon]

Unchained Architecture v3.1:
(it's not nice to explicitly pass the context 3 layers down)

• Core Modules should not know the Unchained API
• Core Modules expose the underlying raw database collections through a standard way to make it easier for user-land code when you need to get a certain product by certain special attributes or do some aggregation.
• All cross-module functions are defined on the "core" umbrella package as "services", an example: instead of doing:

const checkedOut = await modules.orders.checkout(
  order._id,
  {
    paymentContext: {
      receiptData: responseBody?.unified_receipt?.latest_receipt,
    },
  },
  resolvedContext,
);

it should be:

const checkedOut = await services.checkoutCart(
  order._id,
  {
    paymentContext: {
      receiptData: responseBody?.unified_receipt?.latest_receipt,
    },
  }
);

[macrozone]

best base it on nestjs, which already has a good service-layer with DI

[pozylon]

nestjs has some good approaches and also strapi with v3 (v4 not so much in my opinion)