Basic principles to be considered in software architecture __ Architecture

1. Stability principle

The architecture is as simple and clear as possible and not overly designed.

2, attention to isolation treatment

Stable business and variable business to separate processing, the core business and non-core business to separate processing, electrical business and ancillary processes to separate, application and data separation, service and implementation details separation, foreground and background separation.

3. Abstract application relies only on service abstraction and does not depend on service implementation details. Applications rely only on logical databases, and do not care about specific database locations and fragmentation. Apply virtualization deployment, not care about entity machine configuration, dynamic provisioning resources.

4, Loose coupling

Cross-domain invocation as far as possible asynchronous, Non-core business as far as possible asynchronous, you must synchronize the call, set the timeout time and retry mechanism.

5, disaster-tolerant design services to self-government, can be independently modified, deployed, released and managed, to avoid a ripple effect. Through cluster fault tolerant, application system cluster, avoid single point. Multi-machine room disaster-tolerant deployment, multi-live mechanism to avoid single room collapse.

6. What is an architect

Architects, who are first and foremost a system architect with a thorough understanding of the technology and business, may not be able to write specific business implementation logic, but must be familiar with the technology and business flow processes used by the system as a whole, so that the most appropriate architectural design can be given according to the actual business needs. The best architecture is not necessarily suitable for the business, the best for their own.

Second, architects should pay close attention to the technology frontier and be able to use some new technology to change the current complex business, in which the architect assumes the role of the transformative person. A very simple example, a regular project, if not an architect, after half a year can be designed to complete. But the middle may experience a lot of unnecessary duplication of work, and the final product stability may be poor. If there is a competent architect involved, the system may be completed in three months, the period of duplication of work may be reduced, and the final product stability should also be guaranteed. The architect's job should be to anticipate the future and do more proactive work.

The current technical team of many people, according to management of the theory of the range, a manager to manage 8-15 people more reasonable, so that can have enough energy to think about the company strategy, to achieve business, while also have the energy to train talent.