Distributed lottery spike system, DDD architecture design and implementation sharing

Author: Brother Xiaofu
Blog: https://bugstack.cn

Precipitate, share, grow, and let yourself and others gain something! 😄

1. Use large projects to run through the knowledge system

Writing CRUD, stacking APIs, changing shit mountains⛰, and how many 996s you boil are just repeated screws. If you want to break through the bottleneck of existing work and raise your awareness of technology, then you need a large project to run through the knowledge system of common technology stacks. The back eight-legged text of the fragmented fault cannot solve this matter

What to do then? Of course, it is the liver project. The liver is a project with 161dd23f112ed1 having Internet technology system, having distributed architecture application, and having DDD thinking and design pattern practice, so that a skilled person who has not yet been exposed to such projects or who has been stuck in CURD for a long time Work, open your horizons, and grow up quickly.

For half a year , Brother Fu has been doing this, and it was not until today that the first phase of the design, implementation and implementation of the entire system was completed. In this "Distributed Lottery Lottery System" project, I will take you to the DDD architecture and design mode to implement the actual combat method, to carry out code development, video introduction, document description to explain and implement the distributed lottery system , then there will be a lot of DDD design ideas and design pattern applications, as well as technologies applied in the development of Internet manufacturers, including: SpringBoot, Mybatis, Dubbo, MQ, Redis, Mysql, ELK, sub-database sub-table, Otter Wait.

Two, four-tier architecture, domain-driven design

Lottery lottery system project is an Internet lottery system for C-end crowd marketing activities, which can provide logic functions such as creation, participation, accounting, and awarding of lottery game play strategies. In the process of use, the operators create a lottery game for probabilistic prizes to attract new users, activate them, and retain them. Usually, such a system will be used in various scenarios such as e-commerce, takeaway, travel, and official account operations.

1. DDD four-tier architecture

• This system architecture is a four-layer architecture implementation method of DDD domain-driven design. It introduces and shows readers how to develop such code in a way that attaches importance to the implementation of code.
• In the Domain layer, the system process design is gradually disassembled, and the design and development are carried out according to the domain modules of the responsibility boundary, and finally the logic function is arranged in the application layer.
• This system will reflect a lot of design pattern ideas and the final implementation. Only by combining DDD and design patterns can we develop a code structure that is easier to extend and maintain.

2. Distributed Engineering Design

The overall system architecture design includes 6 projects:

1. Lottery: A distributed deployment lottery service system that provides lottery business domain functions and provides RPC services in a distributed deployment manner.
2. Lottery-API: Gateway API service, provided; H5 page lottery, public account development reply message lottery.
3. Lottery-Front: C-side user system, vue H5 lucky-canvas lottery interface, explaining vue project creation, introduction of modules, development interface, cross-domain access and function implementation
4. Lottery-ERP: B-side operation system, which satisfies the operation personnel's query, configuration, modification, audit and other operations for activities.
5. DB-Router: A sub-database sub-table routing component, developed a component based on the core design principle of HashMap, using the method of hashing + perturbation function, hashing data into multiple library tables, and verifying the use.
6. Lottery-Test: Test verification system, a test system used to test and verify RPC services and system function calls.

3. Condensing the process area

• Disassemble the functional process, refine the domain service, and teach you step by step how to disassemble a business functional process into domain modules under each responsibility boundary, and provide the entire service link by connecting the developed domain services in the application layer.
• Through such design and implementation ideas, as well as the use of design patterns to design process-oriented functions in accordance with object-oriented ideas, each step of the code becomes clear and easy to understand, so that the realized code is easier to maintain and expand. .
• Therefore, what you learn in this process is not only code development, but also more landing ideas and practices are reflected in it. It can also lay a good foundation for you to develop such a project in the future or to design ideas for some actual complex scene problems during the interview process.

3. Learning introduction, teach you how to get on the bus

Including: document, video, code, homework, the four aspects are combined to learn, so even students who lack coding experience, fresh graduates or CRUD skilled workers can quickly join the project for learning .

• The course is divided into: Specifications, Domain Development, Operation Background, Application Scenarios, System Operation and Maintenance, a total of 5 chapters and 34 sections to explain the architecture design and practical implementation of DDD distributed system.
• As long as you can follow it carefully, the 22-year offer will not be cheap! really have a difference in R&D capabilities? Actually, no, you are just a large system with someone taking your liver!

1. Study Catalog

• Part 1 Factory Specifications

  • Section 01: Dachang Code Farmer Development Foundation
  • Section 02: How the Demand Comes
  • Section 03: System Architecture Design
  • Section 04: Entering the Development Phase
  • Section 05: System Online Maintenance

• Part 2 Domain Development

  • Section 01: Environment, Configuration, Specifications
  • Section 02: Building the (DDD + RPC) Architecture
  • Section 03: Running through broadcast mode RPC procedure calls
  • Section 04: Sweepstakes Strategy Library Table Design
  • Section 05: Development of modules in the field of lottery strategy
  • Section 06: Template mode handles the lottery process
  • Section 07: Simple Factory Construction Awards
  • Section 08: Configuration and Status of Active Fields
  • Section 09: ID Generation Strategy Domain Development
  • Section 10: Implementing and using sub-database and sub-table
  • Section 11: Declare Transaction Receipt Activity Area Development
  • Section 12: Orchestrating the lottery process at the application layer
  • Section 13: Rules Engine Quantifies Crowd Engagement Activities
  • Section 14: Facade Interface Encapsulation and Object Conversion
  • Section 15: Building the Kafka service environment for the MQ message component
  • Section 16: Using MQ to decouple the lottery delivery process
  • Section 17: Introducing xxl-job to handle liveness scans
  • Section 18: Scanning the library table to compensate for the invoice MQ message
  • Section 19: Designing a Sliding Inventory Distributed Lock Handling Activity Spike

• Part 3 Operations Backend

  • Section 01: UI Engineering Construction
  • Section 02: Activity List Data Display

• Part 4 Application Scenarios

  • Section 01: Building WeChat Official Account Gateway Service
  • Section 02: [homework] vue H5 big turntable lottery

• Part 5 System Operation and Maintenance

  • Section 01: Deploying Docker on Cloud Servers
  • Section 02: Deployment Environment Redis
  • Section 03: Deployment Environment Kafka
  • Section 04: Deployment Environment Mysql
  • Section 05: Deployment Environment xxl-job
  • Section 06: Deployment environment nacos

2. What will you learn

• How to develop distributed system architecture ( RPC , MQ , distributed tasks, sub-libraries and sub-tables)
• The combination of DDD four-tier architecture design and design pattern is implemented
• Code development specifications, requirements review, and operation and maintenance monitoring of Internet giants
• Docker operation and maintenance practices, environment, deployment, configuration, monitoring, logs, etc.

3. Suitable crowd

• R&D personnel with Java programming foundation and want to improve their technical ability
• Hope to improve coding thinking and remove bad smells from code
• Willing to become an architect, but still in a certain bottleneck period
• I want to join a big factory as a code farmer, but I always feel that I can't find a way

4. Join Learning

• Learning link: Lottery lottery system - four-tier architecture practice based on domain-driven design

5. Class representative homework

Honestly, I met someone who understands me!

In the actual project learning, there is a class representative. Each sharing assignment can be described as exquisite. Her learning speed is super fast, and she can also analyze the process of each block very clearly and match the flow chart, as follows:

• I also hope to have more excellent you to learn, grow and make money with me. For 22 years, let's do our best!