The concept of China Platform has been around for years, starting with Supercell, a Finnish gaming company, before Ali came up with the strategy of a big China platform and a small front desk, and then invaded China like a mad dog.

Many small companies in order to appear cool, whatever, dry him, will be hard to fight against the middle out, anyway, there is a name out of the look is very diao.

In fact, however, there is no use, the purpose of the Taiwan or faster to be able to undertake business needs, the release of repeated labor development.

Years also experienced from trade to finance China’s experience, understanding of China is a relatively rough, over the years China really have a so good, even think of what business you want to get into China, now want to do what you want to move on China, as China is everything, not China is able to show their abilities, and not highlight their own level.

Today, I will talk about the central Taiwan, first talk about trading central Taiwan.

China architecture

The birth of any new thing will lead to a series of problems.

For example, I think the initial exploration is nothing more than precipitation and abstraction of general business capabilities to achieve the purpose of fast delivery. Then, with the adjustment of the architecture, the corresponding organization center, technical center, data center and so on will be derived.

Usually, we usually say the most ability is the business, such as the user, commodity, trading, inventory, marketing, financial and so on, these general ability no matter for which company’s business should be an indispensable part.

For the frontend, there are a few changes, such as the concept of BFF (backend for frontend), also known as a front-end oriented backend.

Generally, the requirements for data of different foreground such as C-end APP, PC, H5 and open platform are not quite the same. In order to adapt to these changes, a WHOLE BFF for each end is used as data aggregation and tailoring, and it can also bear some common capabilities such as authentication and flow limiting.

In this way, some traditional gateway capabilities are put together with BFF, which can also be separated. The better solution, I think, is to achieve data aggregation and cutting capabilities through the capacity configuration of middleware, and at the same time, routing, authentication, traffic limiting and so on.

General and abstract capabilities are accumulated in the middle stage, and the original business logic and capabilities are clearly defined. Some traditional business capabilities will be divided into the concept of business background, such as SOME CRM systems, financial management systems, user management and so on.

The architecture is similar to this, and then to the specific transaction of the construction of the middle stage.

Trading in China

The three core parts of the transaction are forward transaction, reverse transaction and contract performance. No matter what abstract ability is done, these three modules are inseparable.

Generally, when the team size is not large, these three capabilities can be maintained together without any problems. The main services themselves can bear the needs of different lines of business, and the three common capabilities can be exported.

Of course, the more specific business should be determined by the business itself, and only the most basic capabilities will be described here.

And when the volume of business increases, it will face more necessary to split, such as order query, order, payment, reverse cancellation refund, performance split form.

Forward transactions

Let me start from the page of the bill of lading, order confirmation page, in general, the bill of lading page information very much, we want to show to buy commodity information, and the level of the user, integral, can use the coupons, price, the rest of the inventory, payment, etc., some still have some for sale of goods, concrete and how to choose the optimal combination, make a tie-in sale presentation logic and so on.

The interface involved in the bill of lading page is a complex abnormality, and the QPS is also high, usually the logic of this interface will be aggregated by a special shopping guide service, of course, there is also the logic of the transaction itself to do this aggregation, but I think it is more reasonable to be aggregated by the shopping guide service.

Other changes are easier to make, and the simple interface to call other services should be satisfied. Since the QPS of this interface will be very high, it is necessary to take measures to degrade the circuit breaker. For services that are not the main link, they must be degraded in the case of high concurrency, and they must not drag down the ordering process of the main link.

Here sell sheet is a more complex part of the implementation is usually in the form of sub orders, also some implementation is an independent parallel orders, still have a plenty of independence to another service, the implementation way don’t do assessment, but complex is really complex, several orders mixed together, to ensure that the final order consistency, must have order is successful, Moreover, it is also very complicated for payment to combine payment and reverse refund.

Page of the bill of lading, he entered the real order payment link, the order process for different business may not be consistent, ability to support in place with the help of a process choreography may be a little bit easy, on the other hand in order to compatible with a variety of different business inevitably need to abstract the general logical enough, but it also makes simple business becomes more complicated.

If everything is if and else for the sake of simplicity, you can also quickly set up shelves, but it will become extremely passive to carry more different business scenarios later.

So the ability to do the existing business should be clear enough after the abstraction, rather than what has not come up to dry tower meow.

Reverse trading

The usual consideration must be closed loop, this word is very good, including our usual design must be the same, light into the PI xiu, as we all know, PI xiu is not chrysanthemum, uncomfortable.

Cancellation of orders, more refund time and payment interaction, for complex business logic, there are various coupons, red envelopes, points, member rights and interests of a lot of deductions will make payment becomes very complicated.

It is very cool when the payment is made. Anyway, the transfer is over. When it comes to the refund, it will be very difficult for different types of rights and interests to be used and profit sharing rules to refund.

The performance

In general, the performance of the asynchronous form will be better. After placing an order, the distribution of points, coupons and red envelopes belong to the performance of the contract, and then the arrangement of distribution, delivery and receipt also belong to the performance of the contract.

The usual form is to monitor the message of successful ordering or payment, and call the interface of the downstream service after consumption. As long as the call is successful, it represents the successful performance of the contract. The final success of the performance should be guaranteed by the downstream service.

Of course, for example, the complicated performance process, involving logistics distribution, it is not so simple.

[PDF] Get 100 computer e-books and interview essence, the article continues to update every week. I’m Ai Xiaoxian, alibaba technology expert, and we’ll see you next time!