Enterprise Informatization Solution--plug-in platform development framework

0, Kick

As a professional programmer or excellent team, has a set of mature, stable development framework, is undoubtedly walking it lake, vertical and horizontal IT market necessary foundation.

No picture no truth, as a pragmatic, ITER, first a few dishes of dessert cold dishes, follow-up will be more hard dishes ~o (∩_∩) o ~

0.1 Platform Login Interface

0.1. Platform Login Interface

The platform login module is designed to take care of both security and ease of use. Only users who are legally authorized and in a normal state can log on to the platform. At the same time, for the convenience of users, in order to ensure that the computer users are relatively unique situation, you can choose to save the login information, the system will automatically encrypt the user's relevant login information after the storage.

0.2 System Setup Interface

0.2. System Setup Interface

The platform provides the basic system configuration and user personalization settings. System settings on the Data Source tab, which provides visual interface settings for the corresponding data source, supports the confidentiality of the data source. supports a variety of common databases (the drop-down list shows the types of databases currently supported: SQL Server, Oracle, MYSQL, Access), servers addresses, database instances, user names and passwords, and so on. After completing the configuration input, you can test the linked server, and after the optimized performance, you can complete the fast response in a short time (no more than 5 seconds).

0.3 Workbench Interface

0.3. Platform Working interface

The whole workbench interface is mainly composed of functional navigation area (user module), Functional work area (user operation), menu bar, toolbar, status bar and several main areas. Navigation and work area is the main area of platform function, and three columns are auxiliary area.

The Workbench interface style of the entire framework platform is borrowed from the universe's Invincible Microsoft Integrated Development Framework (IDE)--visual Studio series, which is estimated to be controversial, but based on my experience with VS and myeclipse development, VS is really easier to use, or more stupid to do. Of course there is no derogatory, the iphone is not also known as a fool will use it ~ so user convenience is the kingly way. Currently can only be Windows invincible, I believe with the increase of Microsoft Open source strength, will eventually become a reality, this is not a dream!

After reading the picture kick, also need the text kick. Next, from a personal point of view, why to develop this set of information-based solutions to the plug-in platform development framework.

First, why is the plug-in? Introduction

The stone of his mountain, can attack Jade, the shoe is suitable or not, only the foot knows.

The rapid development of software industrialization, the ideas and methods of software development are of the same. The team's lean collaboration is an important cornerstone of the growing efficiency of development. An open, highly scalable, parallel development architecture system has become particularly important. In order to meet the production needs of the team, we have built a set of self-developed enterprise-level information Solutions-plug-in framework platform.

In addition to the basic core plug-in framework, the generic plug-in development framework includes workflow components, common permissions system components, auto-update components, custom UI controls, autonomous Orm, and other universal Component system plug-in packages.

1.1 Advantages of a plug-in architecture

The advantages of using the plug-in architecture design are mainly embodied in the following aspects:

1), reduce the mutual dependence between the system modules

Any function module can be developed in the form of plug-in, independent development of each function, there is no mutual interdependence, improve the reusability of functional modules and the flexibility of the entire system. Modifying the function module also does not affect the normal operation of other plug-in modules, which improves the maintainability and expansibility of the system.

2), each module independent development, deployment, maintenance

Each function module is independently developed as a standalone plug-in based on the service interface and related metadata defined by the plug-in contract, each of which completes one or a set of functions. They can have a separate interface, business logic and data access implementation, the plug-in between physical isolation, developers can independently develop functions, independent testing, deployment and upgrade, once the development is completed, the plug-in framework can be mounted in a combination, no longer need to do code merging and overall release.

In theory, plug-in components should not be able to run alone, according to the plug-in architecture principle must be managed by the plug-in manager to run. Actual development may vary depending on the business requirements, and how the plug-in development should be constrained, depending on the needs of the project.

3), dynamic assembly, separation system

The plug-in architecture builds software systems independently and in a modular way, and integrates them at any time during the build process. One or several function modules can be packaged as a separate plug-in for publishing, through a unified configuration file to maintain the deployment information of the plug-in package, the plug-in Manager can dynamically download the corresponding plug-in package (plug-in configuration file, dynamic link library, executable file, etc.) from the server to the client to initialize, combine, and so on. The plug-in framework provides the flexibility to manage the communication mechanism between each plug-in instance and supports hot-swappable loading and unloading.

1.2 Composition of the plug-in architecture

The plug-in architecture design mainly consists of the following three parts:

1, the plug-in framework: the organization and management of the system plug-in download, load, combination, instantiation and destruction, and provide a complete set of communication with the background service interface and other operations.

2, the plug-in contract (service): The plug-in contract in the form of service interface, all the plug-ins of the system through the implementation of the Unified System Framework interface specification, partial to the effective organization, management plug-in objects.

3, plug-in components: the specific plug-in program, the implementation of the plug-in contract service of a separate program.

1.3 Conclusion

The plug-in frame platform optimizes the collaboration between team and team, its parallel architecture can greatly improve the efficiency of software development, reduce the difficulty of design and development, shorten the development cycle, and enhance the operational, testability and maintainability of the application.

Objective: from the perspective of project development, management, release, upgrade and maintenance, a software production line platform based on the plugin warehouse is built.

Enterprise Informatization Solution--plug-in platform development framework