Object-oriented distributed development system
- theoretical articles
March 2003
Summary
In Web application development, the reason why the object can be used, which is convenient to create a flexible, stable web service, attribute to the multilayer architecture of J2EE. In traditional software (non-web applications), how to use object-oriented technology is the main purpose of this article. Based on a distributed development tool model - Softengine, the basic techniques and features of distributed systems, including: task-driven, distributed objects, pipeline design patterns, and data security. More information and related programs download: http://www.snapbug.net
1 Introduction
2. Architecture should have the architecture of the distributed system
3. Key technologies of the layout system
3.1 Object-Oriented Technology Object-Oriented
3.2 Task Drive Task-Driven
3.3 Distributed Object Distributed Object
3.4 Data Security Data-Safety
3.5 Water Wire Forms PIPELINININININING DESIGN Model
4. Improvement of distributed systems for development processes
5. Small knot
1 Introduction
Since its J2EE architecture, web development has become so convenient and efficient based on multi-layer structures such as Bea WebLogic, IBM WebSphere, and Sun ONE. The web program engineer is not too much to care about how to solve system stability, high load, etc., and more focused on how to implement application logic. For example, now, few people have issued issues that are stable, how to expand it after using the above-mentioned middleware products. Because of the J2EE system, these cumbersome technical difficulties have been solved.
Other, non-web way traditional software development engineers have not so lucky. Especially in some basic distributed systems, real-time systems and data transmission systems, web-based applications are unable to resolve. J2EE has no more help. At this point, it can only be developed from the programmer from the system of the most basic function. In addition to function, system performance is good, depending on the quality and experience of developers. Constructing a system like a Web application in a short period of time, making a dream.
In order to achieve this dream, the "bus structure" of the software is born. The so-called bus structure is that all of the functional components are coupled on a structural component used to communicate with each other. The advantage of this is that the internal design of the component is independent, and no need to consider the interconnection problem between the components, the designer can focus on the functional design of the component.
2. Architecture should have the architecture of the distributed system
A Distributed Computing System is a company in real life. Among them, some staff members are responsible for the daily internal affairs guarantee the company's normal operation; some staff are responsible for the relationship with other companies, and define a certain workflow between the company employees, and submit tasks through the form of format. Exchange information. In the company's operation, as long as the employee's responsibilities and workflow remain unchanged, other variable factors, such as work, the physical location or exchange information, will not cause essential changes.
Therefore, in a distributed system, you need to define different functions. These objects are distributable. Objects also need to define information / messages of various contents. Take Softengine as an example, which is set to three most basic elements:
Functional object
(Function Object)
, Responsible for internal functional operations.
Service object
(Serve Object)
And with communication skills.
Task object
(Task Object)
In terms of functional and service objects.
Coordination between objects, information transfer, etc., is packaged in the kernel of Softengine. Various different application systems are evolved by simple interface objects. As shown below, the architecture shown:
Chart 1 THE Architecture of Softengine
Components Area
Component Literature
It is an open area. Provide three main interfaces for the application components
:
Function interface
Function Interface
, Service interface
(Serve Interface)
, Task interface
(Task Interface)
. Inheriting the object-oriented characteristics, the component local area has many "soft bus" characteristics, which can be flexibly loaded, uninstalling the application object.
.
Softengine Kernel
Kernel
Yes
Softengine
The core part, encapsulated most of the internal operation, such as
:
Collaboration between objects, task transfer and distribution management of objects. One of the main two parts
:
Task channel
(Task Channel)
Communication channel
(Communication Channel)
For safety, efficient, accurate transmission data
.
Task Channel
Task channel
Connect each object directly, transfer task information from an object to another
.
Communication Channel
Communication channel
Connect each distribution
Softengine
Kernel. Transport task information from one
Softengine
to another one
Softengine
system
.
Singleton Model
Indirect mode
.
If the application system does not need to be distributed, that is, all application components are posted in the same
Softengine
In the environment, then this separately running mode is alone operating mode
.
GROUP MODEL
Group Operation Mode
.
Based on the single operating mode, application components are distributed in different
Softengine
system. The communication channel is connected to each other, form a distributed system, called
:
Group Operation Mode
.
Softengine architecture, exists in a polymorphic square (single Singleton / Group Group). Synomally fully characterized the characteristics of the softbus; and a plurality of unique groups exhibit distributed system characteristics.
From a single way: is the application software of the soft bus structure, each module (Object Object) is provided on the system through the system, and is published on the system. The objects are coordinated between the objects, and the component operation between the Object is encapsulated in Softengine Kernel.
From the group: It is a distributed structure, each running Softengine system, connects to each other through Kernel, coordinated, becoming a complete powerful distributed system.
Subsequent: Object-Oriented Distributed Development System (2)
