Enterprise-level system architecture design-official Weibo-entlib open-source e-commerce platform

Please pay attention to the official Weibo-entlib open-source e-commerce platform. Our Weibo will often provide some system architecture design, design patterns, IOS iPhone app development, Asp. net MVC, E-commerce system design, and so on.

 

1. users who do not have an idea are afraid of incorrect and impractical ideas;

2. If the software handles all possible stupid errors, it will also create more stupid users;

3. If you want to write a software that can be used by a fool, you can only use it;

 

### Weibo content ###

The benefit of applying SOA in the service layer of the distributed system-the most obvious difference is that service coupling is reduced, that is, the data for operations and interactions complies with the well-defined contract (contract ). In this way, when you modify the internal implementation of the service or even redeploy the service, the client will not be affected.

 

Design that should be avoided in SOA services: (1) Avoid providing more fine-grained methods than business events; If details are exposed outside the service layer, this violates the SOA principles (only share contracts) and causes coupling between the presentation layer and the service layer. (2) avoid disruptive interfaces, that is, the Service exposes a series of fine-grained methods for the presentation layer. The presentation layer must call each other to complete the operation.