Skip to content

Nesting levels of warehouse/workshop relations #4

@motform

Description

@motform

Hi Lin Pengcheng,

First of all, thank you so much for being able to articulate such a correct theory on how build and architect software. It has been a long time coming, and I'm glad someone finally put it all to paper.

Now, I have a question regarding the application of the warehouse/workshop-relationship in the context of a larger system. Specifically, I would like your input on the feasibility of nesting a warehouse/workshop inside of another part of the system, presumably a workshop.

For example, when making food, the supermarket is a warehouse that supplies local households with dry and wet goods. However, in the individual kitchen, could one not also consider the pantry a kind of local warehouse that serves the other ketchen functions? For while the supermarket is the higher level, indeed the super, supplier of perishables, is it perhaps not more pragmatic/simpler to consider the pantry a local workshop in the task of designing an optimal kitchen in accordance to The Pure Function Pipeline Data Flow?

I hope my question and metaphor makes sense, I'm sure you can see how this applies to software development and local/modular integration designs.

Respectfully,

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions