Construction of a large state-owned enterprise technical platform

The company has been compiling a technical platform construction plan for a state-owned enterprise for the whole month.

This enterprise is a 500 powerful state-owned enterprise. They hope to build a unified software platform (technical platform + business platform): various professional departments develop corresponding professional plug-ins based on this platform, and released to the unified plug-in platform, and can be integrated into a unified client software platform, to achieve business components can be reused throughout the company. In addition, in terms of data, we will establish independent private cloud data services for the platform in the second and third phases.

 

Due to confidentiality, many contents of the solution are inconvenient to describe. The following is a summary of some important content of the technical platform in the entire solution.

 

Architectural hierarchy

Peripheral development environment support: VS-SDK, Development Forum, development support, etc.

Application plug-in layer: professional application-level plug-ins.

Basic Application Module layer: the basic application module provided by the platform, including some essential services.

Basic Service Layer: encapsulation layer of basic services.

Basic Framework layer: the basic technical core framework. Includes: plug-in framework, plug-in management module, service container, event bus, interface integration framework, command system, multi-language support, logs, and exceptions.

Data framework layer: domain Entity Framework, object relationship ing, and virtual file access.

 

Interface integration framework

Based on WPF and devexpress, and mvvm as the main architecture mode.

 

Plug-in mechanism

A plug-in framework that supports hot swapping.

Type Selection: the model will be transformed Based on the prism framework.

 

Integration Framework

Service container: built based on the IOC framework.

Event Bus: Use the event mechanism in prism or develop a lightweight event bus.

 

Data Management

Phase I: Map domain entities to local databases/file systems.

Phase II: achieve centralized management of multi-project files.

Phase 3: Implement private cloud data services.

 

Offline scenarios and concurrency support

Upload and download local database + project data.

Both pessimistic concurrency and Optimistic Concurrency are supported.

 

Private cloud interaction Solution

The client-heavy client directly uploads and downloads the overall project data.

The light client obtains the final interface after rendering a large amount of data through the service.

Use Microsoft systemcenter to build a private cloud.

 

Data access framework

Selection: Compare EF and RAFY frameworks.

Use RAFY to map domain entities and databases. Here we can paste two PPT pages:

 

 

 

The above is the main content of the technical platform. The content related to the business platform will not be mentioned here.

On the first day of the National Day, we will explain the entire solution and hope everything will go smoothly.

Construction of a large state-owned enterprise technical platform