On data synchronization from China Telecom and China Mobile's query service

On the last day of June, I wanted to check my package usage. So I sent a text message to the telecom customer service and got a reply like this: "Dear user! The billing cycle is from to on the first day of each month and from to on the third day. You may not be able to query your consumption information. Thank you for your understanding !". I thought, the text message query is like this. Is it through a website query? Go to the official website of China Telecom and enter your account to query the usage of the package. The same response is returned. See:

 

Similarly, I log on to the Mobile official website and perform the same operation, but I can query the usage of the package normally.

 

So we have this article. Talking about data synchronization between China Telecom and China Mobile.

 

I have to say two things before. The first day of every month, to on the first day of every month, and the last day at the end of the month, is the accounting period of the telecommunications system. It takes too long, how many users need to process data? Let's take a look at China Mobile. As far as I know, there is no so-called system billing period of China Telecom, and you can get a quick response at any time (not surprisingly) by querying your package or balance. China Telecom has 0.1323 billion million users, including 41.15 million 3G users, and China Mobile has 0.6616 billion million users, including 56.58 million 3G users. The number of users in China Mobile dumped China Telecom's number of users across several streets. Mobile has such a large user, and the data generated can be imagined, but there is no so-called system billing period, ensuring the real-time user acquisition of information. What about China Telecom? No more.

 

To improve the concurrency efficiency, we can use pessimistic and optimistic locks for control. Pessimistic lock: Implemented by using the lock mechanism of the database itself, you can use the transaction isolation level and reasonably manually designated lock methods according to the specific business conditions, such as reducing the lock granularity and reducing concurrent waiting. Optimistic lock: Use programs to process concurrency. There are roughly three methods: Adding version numbers to records, adding timestamps to records, reading data to be updated in advance, and comparing the data later. Whether it is the locking mechanism of the database system or the Optimistic Locking Mechanism at the business data level, it is essentially a read, write, and judgment of the Status bit.

 

Data access is controlled by locks. We query the plan, execute a SELECT statement, and then update the plan update. How can we maintain data consistency during the SELECT statement, this is what China Telecom and China Mobile need to consider. China Mobile is doing a little better than China Telecom. There is also how to ensure that data is updated in a timely manner within 7x24 hours without a system checkout period. This is a problem that China Telecom should consider. How to synchronize system data in a timely manner is also very important. It is best to choose when the frequency of user activity is low. At any time, users are always the first. If the user experience is poor in some places, it is also very unfavorable for the development of a company.

 

Recommended

Database lock

Database Concurrency Control Technology

My mailbox: wgbno27@163.com Sina Weibo: @ wentasy27 public platform: justoracle (No.: justoracle) database technology exchange group: 336882565 (when adding group verification from csdn XXX) Oracle Exchange discussion group: https://groups.google.com/d/forum/justoracleBy Larry Wen

	@ Wentasy blog is for your reference only. Welcome to visit. I hope to criticize and correct any mistakes. If you need to repost the original blog post, please indicate the source. Thank you for the [csdn blog]