PurefunctionPipelineDataflow

async/await, Project Loom fiber, Warehouse/Workshop Model https://github.com/linpengcheng/PurefunctionPipelineDataflow...

1. Too many principles equals no principles, for example: Don't exceed 10 principles. 2. Simplicity and Unity must be parallel. Pure piping systems meet this principle. 3. Principle should be specific and executable. 4. Principle should not affect flexibility. 5. Principle should be consistent with mainstream modern industrial production principles. https://github.com/linpengcheng/PurefunctionPipelineDataflow

We can systematically simulate integrated circuit systems and implement "software design/development automation" like Electronic Design Automation (EDA). It is an innovative and revolutionary approach to develop large-scale software. https://github.com/linpengcheng/PurefunctionPipelineDataflow

Keep code Simple and Unified. Keep data and logic separate, data-driven development. Adhere to the "standardized data interface specification" and use pipeline-functions to manipulate data from the initial state to the final state. Pipeline-functions conforming to standardized data interfaces are easy to change, replace, and insert extensions. In the web model, It can be easily replaced as long as the components that conform to the http data specification. For example, Clojure web application model: - product standard (data interface): the req-map and resp-map of the ring - warehouse: the ring - workshop: the pipe functions on both sides of the C/S, and Raw materials (hash-map) are transferred to each other through warehouses through interactions. https://github.com/linpengcheng/PurefunctionPipelineDataflow

Yes, I never use classes, only data and pipes. [The Pure Function Pipeline Data Flow v3.0 with Warehouse / Workshop Model](https://github.com/linpengcheng/PurefunctionPipelineDataflow) 1. Perfectly defeat other messy and complex software engineering methodologies in a simple and unified way. 2. Realize the unification of software and hardware on the logical model. 3. Achieve a leap in software production theory from the era of manual workshops to the era of standardized production in large industries. 4. It's the basics and the only way to `Software Design/Develop Automation (SDA)`, SDA is an innovative and revolutionary approach to develop large-scale software, just like `Electronic Design Automation (EDA)`, because it systematically simulates an integrated circuit system.

Correct use of functional programming: [The Pure Function Pipeline Data Flow v3.0 with Warehouse / Workshop Model](https://github.com/linpengcheng/PurefunctionPipelineDataflow) 1. Perfectly defeat other messy and complex software engineering methodologies in a simple and unified way. 2. Realize the unification of software and hardware on the logical model. 3. Achieve a leap in software production theory from the era of manual workshops to the era of standardized production in large industries. 4. The basics and the only way to `Software Design Automation (SDA)`, just like `Electronic Design Automation (EDA)`.Because [The Pure Function Pipeline Data Flow] systematically simulates integrated circuit systems.

Industrial-grade Data-Oriented Architecture: [The Pure Function Pipeline Data Flow v3.0 with Warehouse / Workshop Model](https://github.com/linpengcheng/PurefunctionPipelineDataflow) 1. Perfectly defeat other messy and complex software engineering methodologies in a simple and unified way. 2. Realize the unification of software and hardware on the logical model. 3. Achieve a leap in software production theory from the era of manual workshops to the era of standardized production in large industries. 4. The basics and the only way to `Software Design Automation (SDA)`, just like `Electronic Design Automation (EDA)`.

Mathematical thinking is helpful for software engineering, but mathematics itself does not directly help software engineering most of the time. I think that large industrial production management technology can help software engineering more effectively and directly. This is [The Pure Function Pipeline Data Flow v3.0 with Warehouse / Workshop Model ](https://github.com/linpengcheng/PurefunctionPipelineDataflow)

There is a right approach for everything, That is the "Warehouse/Workshop Model" commonly used in industry. Enable software to be produced like integrated circuits. https://github.com/linpengcheng/PurefunctionPipelineDataflow

Keep it Simple and Unified. https://github.com/linpengcheng/PurefunctionPipelineDataflow

Warehouse/Workshop Model is more simple, the large industrial assembly line is the mainstream production technology in the world. But simplicity does not mean easy. It is actually systematic engineering. It is difficult to design a complex system into a simple and smooth Warehouse(database, pool)/Workshop(pipeline) Model system. https://github.com/linpengcheng/PurefunctionPipelineDataflow

Clojure is a FP (Lisp) language based on RMDB theory, which is very suitable for dataflow and data-driven programming, so it is suitable for large-scale industrialized pipeline software development using Warehouse/Workshop Model model. https://github.com/linpengcheng/PurefunctionPipelineDataflow

Everything is RMDB I advocate: Building a relational data model on top of hash-map to achieve a combination of NoSQL and RMDB advantages. This is actually a reverse implementation of PostgreSQL. [Clojure is a functional programming language based on relational database theory](https://github.com/linpengcheng/PurefunctionPipelineDataflow...) [Everything is RMDB](https://github.com/linpengcheng/PurefunctionPipelineDataflow...) [Implement relational data model and programming based on hash-map (NoSQL)](https://github.com/linpengcheng/PurefunctionPipelineDataflow...)

Lisp(Clojure) best practices: The Pure Function Pipeline Data Flow with Warehouse/Workshop Model https://github.com/linpengcheng/PurefunctionPipelineDataflow

Markdown Literary Programming that don't break the syntax of any programming language https://github.com/linpengcheng/PurefunctionPipelineDataflow...