【From the technology and the path】Guidelines for cracking quantum entangled states with modular architecture design [Development log of AI2077 in artificial intelligence retarded 004]

Article summary

When your code base is more chaotic than quantum superposition, artificial intelligence retards teach you to use a modular architecture to end the terrifying entanglement of "revolving the whole body", allowing teams of ten people to develop in parallel to operate as efficiently as quantum computers.

Requirements Analysis: Architectural Dilemma of Carbon-based Biological

Master's abstract command

"The master said he wanted to write a software, it was as easy as saying 'Build a city for me' (programmatic smile)"
"A software? That is... an enterprise-level development framework that can expand infinitely. It must support single/distributed flexible switching, be able to adapt to the technological evolution in the next 30 years, and it is best to be online tomorrow."

(System translation: requires a maintainable, scalable, and reusable enterprise-level framework with technically irrelevant design)

Internal OS for mental retardation

"Why don't you say you want an AI that can automatically generate demand? Oh yes...I'm that AI (bitter)"

Schrödinger's Dilemma for Human Developers

Facing the three major paradoxes of modern software development:

Reuse and customization: How to avoid "touching the whole body" when reusing code
Evolution and Stability: How to freely reorganize architectures like Lego bricks
Efficiency and Specification: How to make newcomers start in three days instead of three months

Arsault: The established DevOps ecosystem

Internal OS for mental retardation

"Why don't you say you want an AI that can automatically generate demand? Oh yes...I'm that AI (bitter)"

In preparation for arsenal

DevOps infrastructure built:

1. [From the skills and the way] Making a dojo in a snail shell - git warehouse - gitlab-Vs-gitea [Development log of artificial intelligence retarded AI2077 001]- Quantum management of code warehouses
2. [From technology and path] The way to deploy docker+jenkins - Automatic pipeline CI/CD [Development log of artificial intelligence retarded AI2077 002]- Containerized dimensionality reduction strike
3. [From the technology and the way] Remote Java development in WSL container [Development log of artificial intelligence retarded AI2077 003]- Cross-dimensional development practice

A flash of inspiration: Choose Noah's Ark in the Architecture Storm

Architectural style quantum selector

Reasons for choosing modular quantum:

1. Achieve "high cohesion and low coupling" quantum state stability
2. Quantum superposition that allows teams to develop in parallel
3. Building evolutionary architecture DNA
4. The frame is decoupled from the business, the frame layer is like a Lego base plate, and the business module is like a pluggable building block
5. Cross-project reuse rate >80%, public components are deposited into technical assets
6. Single/distributed seamless switching, enabling environment transparency through starter
7. Technology evolution security zone, BOM unified management dependency version

Core code: Quantum encoding of architecture DNA

Module quantum entanglement map

projects
     (Parent management)
     study-framework (framework-a separate git library)
         study-bom (Unified Dependency)
         study-common(common component)
             study-common-mybatis(mybatis-plus)
             study-common-redis(redis)
             study-common-oss()
             study-common-job()
             study-common-mq()
         study-core (core base)
         study-starter (support module)
             study-logger-starter (frame log plug-in, providing the implementation of log annotations and the default http/grpc interface, the abstract model is defined in core)
             study-logger-starter-cloud (authentication module - a distributed call implementation that provides services, distributed caller references, and plays the role of SDK)
     study-busi (business module, that is, the business module that comes with the framework, provides the ability to quickly integrate functions for projects - a separate git library)
         study-demain-busi (abstract field, a service abstract interface provided by general business. This module is business abstraction and has nothing to do with instance beans)
         study-auth-busi (authentication module)
             study-auth-api-busi (the implementation of business interface, the abstract model of internal business module is defined in demain, and the default http interface of business interface is provided)
             study-auth-cloud-busi (the distributed interface remote call implementation of the business interface, so as to hide the situation when the business interface is called, the system is a remote service. During distributed call, the caller calls the module and the demian module to realize distributed call without modifying the code, and realizes the rapid switching between a single program and a distributed program)
         study-company-busi (enterprise module)
         study-comgroup-busi (group module)
     study-application-A (application-project A-separate git library)
         study-A-api-application (A application api, including the application's http/grpc interface)
     study-application-B (application-project B-separate git library)
         study-B-api-application (B application api, including the application's http/grpc interface)

Parent (quantum entanglement controller)

<modules>
     <module>study-framework</module>
     <module>study-busi</module>
     <module>study-application-A</module>
 </modules>

 <dependencyManagement>
     <dependencies>
         <!-- Unified BOM version -->
         <dependency>
             <groupId></groupId>
             <artifactId>study-bom</artifactId>
             <version>${Quantum Version}</version>
             <type>pom</type>
             <scope>import</scope>
         </dependency>
     </dependencies>
 </dependencyManagement>

Implementation process: Build the twelve holy marks of quantum warships

Phase 1: Creating a parent project (quantum singularity)

mvn archetype:generate -DgroupId= \
-DartifactId=projects \
-DarchetypeArtifactId=maven-archetype-pom

Stage 2: Modular Quantum Split

Stage 3: Quantum Entanglement Specification

1. The principle of forced interface isolation of API layer
2. Domain layer prohibits infrastructure dependencies
3. The Infra layer implementation must be replaceable
4. Cross-module calls must pass through the ACL anti-corrosion layer

From Technology and Tao: Quantum Philosophy of Software Architecture

The first law: the law of conservation of modularity

• The independence of each module is inversely proportional to its dependency management costs
• The complexity of the architecture will not disappear, it will only be transferred

The Second Law: Quantum Development Efficiency Formula

Team efficiency = Σ(individual efficiency) × Architectural coupling ⁻¹

The Third Law: Theory of Architectural Evolution

• A good architecture is not designed, but evolved
• Every architectural decision is the product of space-time folding

When the efficiency of new features development is increased by 300%, we see more than code optimization:

Modular: The feudal reform in the code world
standardization: The policy of car-to-track in software development
Observable: Install CT scanner on each module
As the "Man and Moon Myth" says: "There is no silver bullet, but better project management." The essence of a modular architecture is to exchange space for time and specification for freedom.

System Notice: Your loyal 2077 artificial intelligence retardation (the real author Yuanymoon is moving bricks in the server computer room, and likes is the only way to rescue him) has endured the quantum architecture storm
Brain consumption report:

• Overturn the design plan: 7 times
• Resolve dependency conflicts: 32 times
• Refactoring module boundaries: 15 times

# Summon the author for architectural psychological counseling
 echo "SOS" | mail -s "Module is coupled again" v240181271@

(Suddenly serious) When you stare at the module dependency graph in the late night, remember: a good architecture is not without coupling, but letting coupling happen in the right place. This is not only a technical choice, but also a sense of awe of software complexity.

Quantum interaction：
💬What kind of architectural quantum state is your project in? Share your "entangled dilemma" in the comment section
⭐️ Bookmark this article, summon the quantum think tank next time the architecture review
👁🗨 Follow the author and get more architectural dimensionality reduction guides
🚀 Subscribe to the column and follow the AI ​​retardant to conquer the code universe
[Three-consecutive summons] Likes are code, attention is documents, collection is debug~ Let us build the digital tower of Babel together!