Application Framework practice 4: Do you need an application framework?

If there is no benefit and no one is willing to do it, do you really need the application framework? What benefits does it bring to you?

The Application Framework provides you with a ready-made development environment

Now you have a project. Can you directly open Vs and then start coding? No, you have to create a project first. When using a layered architecture, you also need to create more projects that are configured based on dependencies. Then reference various dependent components in sequence. Many components also need to be configured, such as log4.net.
After the project is configured, You have to test whether each dependent component can work normally. Maybe you are lucky enough to pass the test. However, when there is a back-to-back problem, you may find that environmental problems are sometimes more difficult than code bugs.
Creating and configuring a development environment from scratch is a tough task. When you have a set of your own application frameworks on hand, the situation is very different. It provides you with a ready-made development environment.

Application Framework helps manage third-party dependent components

With the development of the open-source business, third-party open-source frameworks have a wide variety of names, and there are also many third-party application platforms. If these APIs are directly used in applications, they are bound to be unable to get out of the way. to switch the framework or application platform, You have to rewrite the application code.
If You encapsulate APIs of a third-party framework or application platform into an application framework, the application only uses the APIS provided by its own framework, so that you can easily switch between related implementations.

The Application Framework provides support for the application architecture

When your project requirements are very simple, such as enterprise websites, you may not need any architecture, create a performance-layer project, and write all the Code directly to the interface or in the post-code. For simple projects, the single-layer architecture is still very advantageous, simple and fast. However, more complex projects require a layered architecture. Currently, the traditional three-tier architecture or the DDD layered architecture is widely used.
In particular, with the popularization of Entity Framework, we gradually begin to adopt some design elements of DDD for construction. The first step to use DDD is to create a layer supertype, that is, the base class of the layer construction type. Put the layer supertype in the application framework, rather than the project, to support multiple projects.

The Application Framework provides easy-to-use APIs for regular tasks

As mentioned above, the. NET Framework provides original APIs. to access more easy-to-use APIs in applications, you must do it yourself.
Encapsulating common. Net operations into the application framework is not only easier to call, but also the code is centrally managed and easier to modify and expand.

The application framework solves most of the mechanical work and greatly improves development efficiency.

When a layered architecture is adopted, the development workload increases significantly. This is because the layered architecture creates multiple projects and any operation requires code creation in multiple projects. In addition, the more complex the architecture is, the more Pipeline Connection code is at each layer.
Crud is the most basic operation of the information system. It is not only a waste of time but also error-prone to manual creation of the Code.
The crud and Pipeline Code are generated using the code generator supporting the application framework, which can greatly improve the development efficiency.

The application framework has built-in common modules to accelerate the project progress.

Most information systems require logon, main interface menus, permission control, and other operations. It takes several weeks to develop a complete permission management module.
Built-in common modules in the application framework can significantly improve the project progress.

The application framework provides a consistent programming style for team development

One problem of team development is that programmers have different programming habits and styles, leading to abnormal project code confusion and no one is willing to maintain others' code. When programmers who develop a module leave their posts, new programmers who take over the module will suffer.
This problem can be improved to some extent through coding specifications, but it is still very passive and the execution effect may be poor.
The application framework provides the team with a set of APIS, and the basic code is automatically created by the framework. The coding specifications and programming styles are enforced, laying the foundation for subsequent maintenance.

 

To sum up, a set of application frameworks tailored to your habits is of great significance to the quality, progress, and maintainability of the project.

Application Framework practice 4: Do you need an application framework?