TikTok-style architecture: should be understood as a feed ranking pattern, not an internal diagram

Aug 16, 2022 3 min read

Introduction

The phrase “TikTok-style architecture” sounds very appealing, but it’s also easy to overstate.

Without official engineering documentation, one shouldn’t draw a diagram and assert “TikTok uses Kafka/Flink/feature store like this”. That’s making things up.

A safer approach is to look at what TikTok publicly says about the For You feed, and then derive common patterns of a modern feed ranking system.

1. What does TikTok officially say?

TikTok says the For You feed is personalized for each user. The system recommends content by ranking videos based on multiple factors, starting from the interests users express, and then adjusting according to what the user is interested or not interested in.

The signals mentioned include:

  • user interactions;
  • video information;
  • device/account settings.

TikTok also says they try to diversify recommendations, not just repeating the same type of content a user has liked.

2. Patterns that can be derived

From public sources, we can say a feed ranking system usually needs:

User signals
→ Content candidates
→ Ranking
→ Diversity / safety rules
→ Feed result
→ New feedback signals

In which the feedback loop is a very important part. Users watch, swipe, like, follow, comment, click “not interested” — all of these become signals for the feed to continue adjusting.

3. What should not be asserted

Should not write:

TikTok uses Kafka and Flink for real-time recommendation.

If there are no official sources or clear technical papers.

Can write more cautiously:

A real-time feed ranking system often might need event streaming and stream processing. Kafka/Flink are two popular technologies for this group of problems, but TikTok's public sources are not enough to assert that TikTok uses them in a specific way.

This is the difference between responsible technical analysis and guessing.

4. Applying to CRM/AI workflows

A CRM can also learn the feed ranking pattern, but at a smaller scale:

Lead events
→ Candidate next actions
→ Scoring/ranking
→ Business rule
→ Suggested action
→ User feedback

For example, if sales ignores a suggestion or a customer doesn’t respond, the system should record it. If a quote is opened multiple times, the lead can be prioritized higher.

5. Conclusion

“TikTok-style architecture” should be understood as a pattern about feedback-rich products, personalization, and continuous ranking, not an internal diagram of TikTok.

When writing technical blogs, an important part is knowing the boundaries: what the source says, what we infer, and what we are not allowed to assert.

References

New posts, shipping stories, and nerdy links straight to your inbox.

2x per month, pure signal, zero fluff.


Share this post on: