Repository navigation
Nesting levels of warehouse/workshop relations #4
Description
Activity
My
Warehouse/Workshop Modelcan 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:nested
-
-
- Warehouse ...
- 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)....
- Warehouse ...
-
integrated
- The unification with Information System Integration Model
- M1 Ultra is a mistake, the memory interconnection is better than the chip interconnection.
integrated or splited
- The unification with OO&FP
- We can split a large system and evolve it into a microservice system......
- We can integrate many independent systems and evolve it into an integrated system......
Reacted by Elias Sjögreen, Fritiof Rusck, Alex Mingoia and Love Lagerkvist-
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/workshopinside of another part of the system, presumably aworkshop.For example, when making food, the supermarket is a
warehousethat supplies local households with dry and wet goods. However, in the individual kitchen, could one not also consider the pantry a kind of localwarehousethat 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 localworkshopin 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,