ArticleDirectory
- Problem fields covered by DSS
Original article link
Decentralized Software Service (DSS) is a lightweight. Net Runtime Environment Based on CR. DSS provides a lightweight, State-oriented service model that combines rest concepts with system-level methods for constructing high-performance and highly scalable applications. In DSS, a service is exposed to beProgramAnd resources accessed on the UI. Through integration: Status isolation, structured State operations, event notifications, and conventional service combinations, DSS solves the need to write high-performance, observed, and loosely coupled applications running on one node or across networks.
DSS is designed primarily to combine performance, simplicity, and robustness. This makes DSS very suitable for creating applications composed of service aggregation, whether the service runs on the same node or spans the network. This goal makes DSS a flexible and simple platform that can be used to write a variety of applications. DSS uses the decentralized service protocol (
Decentralized software services protocol (dssp) As the basis for interaction between services. Dssp is a lightweight soap-based protocol that provides a clear and symmetric state transfer application model that supports State operations and an event model driven by state changes. The DSS provides a host environment (hosting environment) during runtime ), this environment provides built-in support for service combination, publishing/subscription, lifecycle management, security, monitoring, and logs on the same node and across networks. Services can be written using Visual Studio or Microsoft Visual Programming Language (VPL. VPL can drag a service to the canvas and connect the service together based on the data dependency to create a simple service combination application. In addition, the DSS manifest Editor provides a graphical environment for connecting (wiring up), configuring, deploying, and running DSS applications on one node or across networks. The problem areas covered by DSS Below we will discuss three common application programming problem areas and how DSS can solve them: Strong Robustness in any responsible system, failure of a part of the system may lead to paralysis of the entire system. This is because part of the failure, if not properly isolated, detected and processed, will lead to catastrophic failure. Loose coupling is a common design pattern used to limit the impact of partial failures. However, to construct a loosely coupled system, each component must be isolated from other components and be isolated from the underlying runtime environment. Two common isolation methods in system failure are data isolation and operation isolation. A lack of data isolation will cause the internal status of the service to be damaged, and a lack of Operation isolation will cause the formation to lose response. DSS isolates services on both data and operation. Data isolation is achieved by completely cloning messages exchanged between all services (including system services. Clone Code As part of compilation, it is much faster than full serialization. The demand for combiner robustness forces the program to be a combination of a group of loosely coupled components. This raises another question: how to identify, locate, and combine these components into a running application. Most traditional systems define an application as a single process instead of a group of loosely coupled services that work together. This leaves the combined tasks to the Application designers. DSS supports creating, managing, deploying, and running applications composed of loosely coupled services by protocols and runtime. The service is created at runtime and connected according to the descriptions of other services that it needs to combine to ensure proper functionality. This model allows the application to configure where the strength of each service runs at runtime. In addition, the relationship between each service instance and other service instances can be exposed through dssp, which makes it possible to see the service instances on which any specified service instance depends. Observability
An important aspect of all applications is that you can know what it is doing, what it is in, and how it reaches this state. Simply put, a system that cannot be observed cannot know whether it functions normally. By defining a service as a resource identifier expressed by a URI and exposing the status of the resource (which may be changed by internal service behavior or by interacting with other services ), DSS places the observability concept at the core of its application model. However, the concept of observability goes beyond monitoring applications simply by detecting the state of the service. By exposing services in a unified manner based on service statuses, DSS provides a simple and consistent solution for processing management, security, and status-based service combinations. DSS also allows each DSS service to be accessed through the browser UI and easily integrated with a variety of common tools and platforms.
Start
As part of DSS, we provide a large number of different examples and guidance, the demonstration covers simple applications such as "Hello World" from the beginning to complex applications that can run smoothly on the same node or across networks.
