1. Thinking
1. Thick platform, thin business
2. Business positioning of the service center:
Relevant services are provided by their own service centers. No matter how diverse the front-end business forms are, the services provided by the shared service center can well provide the core services included, allowing the transaction information of the front-end business. And the data is returned to the corresponding service center.
3. Business Architect: (service center business person in charge)
From the initial test of technology development, in the infiltration of the needs of the business field for many years, he has continuously formed a comprehensive knowledge system and his own understanding of the business, and the functional positioning of the business in the group. , The market development trend has a certain overall understanding, and can lead the team from a business perspective to build the core capabilities of the service center, professional and mature direction.
4. Business architects' concerns and thinking
- in the current business process design, what applications and services do I rely on?
- What is the dependency path of the entire link? Which services are the most central to current business processing? If these dependencies are wrong, what is the impact on members?
- Where is the time spent processing a business request? Whether it is because a certain service takes a long time, or a certain database access operation takes the longest time, a clear and intuitive positioning is required.
- In the business link I am responsible for, which services have a high error rate in the past period of time, and which services are the processing bottlenecks of the business link?
2. Building a shared service system
1. Distributed service framework: slightly
2. Design of service center:
- High cohesion, low coupling
- Data integrity
- Business operability
- Asymptotic construction
3. Data splitting: sub-database sub-table, heterogeneous index, search engine
4. Principles of asynchrony and caching:
- Asynchronous mechanism based on message service
- Idempotency: the same operation is performed repeatedly, and the result remains unchanged
- Two-phase commit protocol
- TRY/CONFIRM/CANCEL
- Optimistic locking
- Message service update cache
5. Digital operation:
- Distributed service call chain tracking platform (Eagle Eye)
- Massive log distributed processing platform (TLog)
6. Build platform stability:
- Online stress testing tool
- Current limiting component (TMD Taobao missile defense system)
- Current limiting platform (Sentinel), resources and strategies
- Traffic scheduling
- Service switch management platform (Switch)
- Full link Stress Testing Platform
- Implement Business Auditing Platform (BCP), combine messages/logs into events, and run event information rules
7. Management services
- online and data-based service capabilities
- componentized services
- API service encapsulation
- API -> Product -> Solution
8. Capability openness is the foundation for building an ecosystem: active participants and continuous innovation.
3. My understanding
This book answers at least half of a question: how to build a system for enterprises, especially non-Internet companies, to better support the original internal service system to go out, realize external services, and realize a shared service platform.
The key lies in the construction of the middle office, building a front desk for the company's business, building a middle office for the industry field, and adopting a general and mature background is one direction. In this way, after timely business precipitation, middle-office services can be pushed to the entire industry, and an ecological platform can be built to support the special front-end needs of each client company.
Key words: Precipitation The precipitation of
technology , the precipitation of talents, and the precipitation of business accumulation can all be supported under the framework of Zhongtai.
Difficulties and talents: need to have excellent business architects to support