soa principles of service design

Architecture Design for restREST (representational state Transfer) is a lightweight Web service architecture style that is significantly simpler to implement and operate than soap and XML-RPC, and can be implemented entirely via the HTTP protocol. Cache caches can also be used to improve responsiveness, better performance, efficiency, and ease of use than the SOAP protocol.The rest architecture follows the

Distributed design and development (iii) ------ high consistency service ZooKeeper, In a distributed environment, most services allow partial failures and data inconsistency. However, some of the most basic services require high reliability and consistency, these services are the basis for other distributed services, such as naming service and distributed lock. T

mark (where the user doesn't understand it) increases our cognitive burden and pulls our attention away from the task to be done. This kind of interference may be slight, but they accumulate, and sometimes this kind of interference is not enough to make us mad. Besides, people usually don't like to think about the underlying principles. The people who build the site don't make them understood (and easy to use) will make us lose confidence in the site

Interface Design principle interface type Simple data query interface: Action, façade, DAO with business logic data query interface: Action, façade, biz, DAO simple Data Write interface: Action, façade, DAO with business logic data write interface: action, Façade, biz, DAO Synchronous Interface design principles for asynchronous interfaces Interface coarse graine

In the previous chapters, we analyzed the design and implementation principles of the service-side system, in which we use the server-side framework to implement a chat system that runs in the intranet environment. The chat system consists of two parts: client and server, and the service side maintains the user's accou