You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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,
The text was updated successfully, but these errors were encountered:
My Warehouse/Workshop Model can be a fractal system that perfectly simulates the entire manufacturing ecosystem, so that the models can be nested or integrated or splited, as can be seen in the following link:
It can have no container, at this time it is just a dispatch center (Virtual Unified Warehouse, integration layer or platform, the parent company of the enterprise group)....
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 awarehouse/workshop
inside of another part of the system, presumably aworkshop
.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 localwarehouse
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 localworkshop
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,
The text was updated successfully, but these errors were encountered: