dainamite-layering

Optimal code placement in a multi-layer architecture depends on feature reusability and specificity. This Skill evaluates whether new code should be customer-specific, reusable across customers, or contributed upstream.

The Dainamite 3-layer architecture is a structure dividing code into L1, L2, and L3 layers. It ensures application maintainability and scalability by separating customer-specific code from reusable and upstream modules.

To identify the correct architectural layer, follow a decision tree evaluating code reusability. L1 handles customer-specific code, L2 contains multi-customer reusable modules, and L3 is for upstream contributions.

Packaging rules for promoting L2 modules from L3 require evaluating code reusability across multiple customers. The Skill provides specific guidelines to transition upstream code into multi-customer reusable packages.

Yes, you need basic coding knowledge and an understanding of the Dainamite 3-layer architecture. These prerequisites are required to effectively use the decision framework for choosing the correct code layer.

You should not place reusable code in the customer-specific layer if it serves multiple customers. Use the decision framework to promote such code to L2 or contribute it upstream to L3 to maintain scalability.