The unification of Microservice, DB, OOP, FP and Warehouse/Workshop Model
Tags: microservices, architecture, systemdesign, programming
Published: 2024-05-05 01:33:36

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/dorev08zfqmtadj7g9z5.png)

### The unification of Microservice, DB, OOP, FP and Warehouse/Workshop Model

>  Programs = Algorithm + Data Structures
>  ---- Niklaus Wirth, Turing Award (1984), Father of Pascal
  
>  It’s better to have 100 functions operate on one data structure than 10 functions on 10 data structures.        
>  ---- Alan Perlis
>  the first recipient of the Turing Award (1966)
>  A founding father of Computer Science as a separate discipline

- **Warehouse**: Dataservice, Data Management, Object state, Data Structure, database. Obviously, the database should be as global and unique as possible.
  
- **Workshop**: Microservices, Independent Systems, Object method, pure function (functional pipeline), Algorithms.

### We can split a large system and evolve it into a microservice system.
  
- **Warehouse**: Object state, dataservice, data management

- **Workshop**: Object method, Microservice, Various independent systems.

See also: [The unification of `Microservice` and `Intelligent-thread`](https://github.com/linpengcheng/PurefunctionPipelineDataflow#The-unification-of-Microservice-and-Intelligent-thread)

### We can integrate many independent systems and evolve it into an integrated system.

Many large enterprises have independent information systems produced by different manufacturers and need to integrate. We can integrate many independent systems and evolve it into an integrated system.:

- **Workshop**: Object method, individual subsystems

- **Warehouse**: Object state

  - The information system integration layer acts as a individual system

  - A unified abstraction layer (virtual database, virtual data warehouse) of enterprise global data, external data requests for any subsystem are requested from warehouse(virtual unified db) without knowing which other subsystem to obtain them from. Achieve the unity of the global system.

  - The middle layer and data routing of system interconnection.
  
See also: 
- [The unification with `Information System Integration Model`](https://github.com/linpengcheng/PurefunctionPipelineDataflow#The-unification-with-Information-System-Integration-Model)
- [10 Principles: Single Leader and Unified Scheduling](https://github.com/linpengcheng/PurefunctionPipelineDataflow#Single-Leader-and-Unified-Scheduling)
- [Overview of the Warehouse/Workshop Model](https://github.com/linpengcheng/PurefunctionPipelineDataflow#Overview-of-the-model)
  - Warehouse ...
  - It can have no container, ... 

so, Workshops (object method, microservices, independent systems) are decentralized and independent, but The workshop is connected with data services (object status, warehouse) to form a system (large object).

----

> It is the perfect theory if a theory is based on mathematics and meets the five basic principles of "Simplicity, Unity, Order, Symmetry and Definiteness" in science, industry and aesthetics.  
> 
> Traditional IT theory (OOP, FP and hardware architecture, etc.) are pseudoscience. they belong to what physicist Wolfgang Pauli said "Not Even Wrong".
> 
> Keep it Simple and Unified.
> 
> Computer science is essentially a management science, and vice versa.
> 
> Software and hardware are factories that manufacture data, so they have the same "warehouse/workshop model" and management methods as the manufacturing industry.
> 
> ---- Lin Pengcheng

### Reference

- [2018.03.18, The Math-based Grand Unified Programming Theory: The Pure Function Pipeline Data Flow with Principle-based Warehouse/Workshop Model](https://github.com/linpengcheng/PurefunctionPipelineDataflow)
            
- [The unification of OOP, FP and Warehouse/Workshop Model](https://github.com/linpengcheng/PurefunctionPipelineDataflow?tab=readme-ov-file#The-unification-with-object-oriented)

- [Traditional IT theory (OO, FP and hardware architecture, etc.) VS. Warehouse/Workshop Model](https://github.com/linpengcheng/PurefunctionPipelineDataflow#Traditional-OO-and-FP-architecture-VS-Warehouse-Workshop-Model)

- [The unification with `Information System Integration Model`](https://github.com/linpengcheng/PurefunctionPipelineDataflow#The-unification-with-Information-System-Integration-Model)

- [Success Story](https://github.com/linpengcheng/PurefunctionPipelineDataflow/blob/master/doc/SuccessStory.md)