WCF Service Programming Design Specification (2): Preamble, general design specifications and essentials

WCF Service Programming Design Specification (2): Preamble, general design specifications and essentials. Main translation collation, preface, WCF Design general design specifications, design points. and give a comment. The comment is enclosed in parentheses. The next section will be sorted, service contract, data contract, instance management content. Here is a bilingual version of Chinese and English. Convenient for everyone to learn. At the end of the translation, I will arrange a pure Chinese version to release. If there are any mistakes, please criticize them. Welcome message exchange.

Preface

A complete coding specification is critical for a successful product delivery. This specification helps to reinforce common best practice guidelines and to avoid making mistakes that make it easier for the entire team to understand this knowledge. Generally, coding specifications are quite cumbersome, hundreds of pages, the content of the detailed description of the rationale for each coding rule. Although this is much better than no specification, it is often difficult for developers to understand and master. Instead, the WCF coding specification only has more than 10 pages and details "what" and "why." I believe that to fully understand the essence of each coding rule and apply these rules properly, you need to read a lot of books and years of work experience. When a newcomer enters the team, you can quickly tell him or her to "look at the spec first". Because it takes time and this year's speech to fully understand these norms, and we should follow it before that. Here are some common rules, flaws, guidelines, and recommendations. The best practices and helper classes described in WCF Master Class and programming WCF services (which are proficient in WCF curriculum and WCF service programming) are used here.

Juval Lowy

General design Guidelines

General Design Specifications

1.ALL services must adhere to these principles:

All services must adhere to these principles:

A) Services are secure.

The service is safe.

b) Service operations leave the system in a consistent state.

Service operation to ensure that the system is in a constant state.

c) Services are Thread-safe and can accessed by concurrent clients.

The service is thread-safe and can be accessed by concurrent clients.

D) Services are reliable.

The service is reliable.

e) Services are robust.

The service is robust.