Becoming Rich with Daily Scavenging APP

Chapter 763 753_2



Chapter 763 753_2

"If the internet really collapsed everywhere except Huaxia, wouldn't our internet become the world's last hope?" Chen Yiyang couldn't help but joke."That's not quite the case," Wen Liangfeng replied, "But with such a widespread collapse, it must be a problem at some critical point. Preliminary guess, it might be Cloudflare."

"What's that?" Chen Yiyang asked.

"I'm busy right now, I'll call you in a few hours and explain," Wen Liangfeng got back to his tasks.

After finishing his own work, Chen Yiyang went home.

The next day, Wen Liangfeng finally called Chen Yiyang.

"Did you know the internet abroad was down for a few hours last night?"

"How long?" Chen Yiyang hadn't continued following the situation. But based on his usual experience, he guessed it would be one or two hours.

"A full six hours," Wen Liangfeng said.

"That long?" Chen Yiyang was a bit surprised.

"The reason is just as I guessed yesterday, it was indeed Cloudflare's collapse that caused the entire foreign internet to shut down for six hours."

After saying this, Wen Liangfeng explained to Chen Yiyang what Cloudflare is.

To compare Cloudflare's importance to the internet using institutions anyone would know, it's like the property management company for the entire internet, responsible for the security, acceleration, and traffic management of various websites.

Under normal circumstances, when a user uses the internet to visit a website, the browser should directly connect to the website's server.

But if the site uses Cloudflare, the process changes. Your browser will first access but if the website used Cloudflare, the process transforms into, and then Cloudflare accesses the website's server and returns to your browser.

The reason for taking this detour is that Cloudflare has deployed over three hundred data centers worldwide, allowing you to access websites through them, guiding you to the nearest data center for much faster access speeds.

It's like online shopping, where originally the manufacturer directly ships to you, but with Cloudflare, it becomes delivery from Cloudflare's local warehouse, much faster.

Besides, Cloudflare also provides security services to various websites, preventing hacking, crawlers, and caching website content to reduce server pressure.

So Cloudflare is like the property manager of all websites, and ordinary users need to pass through it to verify whether you are a legitimate user when browsing.

If you are, it straightaway lets you take the elevator directly to your destination, much faster than walking.

But yesterday a small thing happened.

Cloudflare itself crashed.

The reason for the collapse was provided in an incident report from Cloudflare itself.

The reason was quite ridiculous.

Cloudflare has a function called bot management, responsible for identifying whether users visiting websites are bots and assigning scores to each user.

Only users who achieve the designated score can normally access the site.

This function is primarily to prevent malicious users or bot users from competing websites.

Different websites have different user entry scores.

For example, ordinary content sites or news sites, users just have to resemble humans, as these sites need traffic.

Whereas e-commerce sites require very high user scores because such sites have many bots disrupting normal user experiences like snapping up deals.

All user scores are evaluated every five minutes.

Each time a user attempts to log in to a site, Cloudflare's scoring module sends the user's score to the auditing module.

However, last night Cloudflare underwent a minor update.

After this update, when the auditing module requests user scores, it no longer requests from a single node, but from all nodes on the platform.

Originally, it would receive about sixty feature lists when requesting scores.

But now, a pile of nodes sent feature lists, causing the list data to exceed two hundred instantly.

And Cloudflare platform's preset safety upper limit for feature lists was only two hundred.

Now with the limit suddenly bursting, the whole system blacked out and crashed automatically.

And it didn't stop there.

Due to Cloudflare's massive scale, database updates occur in batches.

Initially, some websites were lucky and received normal data, while others weren't as lucky and got data exceeding the limit.

The result was that all websites online sometimes could connect, other times couldn't.

Then Cloudflare's engineers saw this and thought the platform was being network attacked.

So initially, the entire company's engineers repaired the system under the assumption of a network attack.

Of course, that didn't work.

Only after a few hours did they realize a bug occurred during the update.

Thus, they hurriedly began reverting all nodes to the previous version.

As mentioned earlier, Cloudflare operates in batch updates. Hence, the recovery process was slow, too.

Restoration started at two twenty and ended at five when all nodes and servers returned to the old version, ending the outage.

This massive internet collapse lasted a full six hours.

The scale of the outage losses hasn't been calculated yet.

However, the previous global internet outage due to AWS affected over sixty countries, seventeen million users, and more than thirty-five hundred companies.

The final tally showed the global loss was seventy-five million US Dollars per hour.

The losses from this Cloudflare outage will only be higher, not lower.

Nonetheless, upon confirming the outage didn't affect his company, Chen Yiyang didn't pay much further attention and chatted with Wen Liangfeng about other topics instead.

"Recently someone on my social platform commented that DeepSeek's response speed seems slower, and its depth of thought isn't as good as before, suspecting it has lowered its intelligence; what's going on?"

"How to say." Wen Liangfeng hadn't expected Chen Yiyang to ask about this, so he thought it over before answering,

"Currently our major model's target customers are not ordinary internet users but those research companies. Therefore, we reduced performance for ordinary users."

"Research companies?" Chen Yiyang asked.

"Exactly." Wen Liangfeng continued, "We are collaborating with some medical companies, using the major model to shorten their research cycles in pharmaceuticals.

For example, recently we assisted a company in bio data analysis, target discovery, molecular design, and clinical trial optimization.

Originally, this company took around five years for the target discovery process.

But now with big data, it only takes eighteen months to complete the entire process.

Additionally, in clinical trials, through our optimization, the original success rate increased from ten percent to eighty percent.

Collaborating with these types of research companies not only increases company revenue but also further enhances the capabilities of the major model in industrial technology.

However, the company's computing power is limited, so inevitably sometimes performance is reduced for ordinary users."

"I see." Chen Yiyang nodded.

Wen Liangfeng's choice was sound.

Considering DeepSeek hasn't gone public, funds are limited.

And in the future commercial market, the integration of major models with industrial technology holds more prospects and profitability.

DeepSeek's choice certainly makes sense.

Many foreign AI major models rely on investor money, so they strive to enhance the user experience for ordinary users to capture the market.

It's a difference in choices, nothing to criticize.

After finishing his conversation with Wen Liangfeng, Chen Yiyang hung up.

Then, looking at his phone, Zhang Yuling had sent him a message.

"My company is experiencing some trouble in France; if you have time, please give me a call."

France?

Chen Yiyang frowned.


Tip: You can use left, right, A and D keyboard keys to browse between chapters.