1. Code templating

The rapid development framework generally has a uniform code style, the same layer of different types of code, are similar to the template structure, convenient to use template tools to generate unified, reduce a large number of repeated code writing. When learning, usually as long as you understand a representative class of a certain layer, it is equivalent to understanding the structure and function of most other classifications of the same layer, which is easy to get started. Different members of the team use the same invocation style to code, which greatly improves the readability of the code and facilitates maintenance and management.

Img1.sycdn.imooc.com/5ef0c271000…

2, reuse,

Rapid development framework generally clear levels, different developers will according to the specific function in the same position, and cooperate with the development of the corresponding documents and code reuse will be very high, what want to invoke functions directly into the corresponding location to find related functions, rather than each developer to write a set of the same method.

3, high cohesion (packaging)

The functions in the rapid development framework will achieve high cohesion. Developers will package various needed functions in different layers for everyone to call, and everyone does not need to be clear about the implementation of these methods when calling, just need to pay attention to whether the output result is what they want.

4, specification

Img4.sycdn.imooc.com/5ef0c27e000…

When developing a rapid development framework, it is necessary to strictly implement code development specifications, such as naming, annotation, architecture layering, coding, and documentation. Because the framework you develop doesn’t have to be your own, it’s important to make it easier for others to understand and master.

5. Scalability

Scalability must be considered when developing a framework quickly. As the business logic becomes more complex, the volume of quantitative records explodes, and the amount of concurrency increases, can it be accommodated with small adjustments? Or do you need to tear down the whole framework and start from scratch? Of course, for small and medium-sized project frameworks, you don’t have to worry too much about these things, but when you have enough skills and experience, you will naturally pay attention to the details of development.

Img4.sycdn.imooc.com/5ef0c28d000…

6, maintainable

Mature rapid development framework, for secondary development or maintenance of existing features, should be very easy to operate. For example, adding, modifying, or removing a field or related function in a project can be done in ten minutes or less. Adding a data table and corresponding functions can also be done quickly. Function changes and modifications do not adversely affect the system. Code is not hard coded and so on, ensuring productivity and quality of software development

7. Collaborative development

With the rapid development framework, we can organize large and small teams for better collaborative development, mature framework will greatly reduce the difficulty of project development, speed up development, reduce development costs, reduce maintenance difficulty.

Img1.sycdn.imooc.com/5ef0c2bc000…

8. Versatility

Rapid development frameworks in the same industry or domain have similar functionality and can be applied to similar projects without major changes. In the rapid development framework, we generally implement some homogeneous basic functions, such as permission management, role management, menu management, log management, exception handling…… Or the generic functionality to be used in the industry, so that the framework can be applied to an industry or domain, rather than specific to a company or business. (Of course, there will certainly be frameworks for specific functionality, but this is a very rare case, not the scope of our consideration.)