Design Concept of image and text live broadcasting

I just raised a question. Some people have said that the description is not clear. Now I want to introduce how to implement a new text-and-text live broadcast, just like the common online [graphic live broadcast of a new product launch, what is a good design to deal with this high concurrency in a short period of time? I just raised a question. Some people have said that the description is not clear. Now I want to raise a new one.

How does text-and-text live broadcast come true, just like the common online [text-and-text live broadcast of a new product launch]? What is a good design to deal with this high concurrency in a short time?

Reply content:

I just raised a question. Some people have said that the description is not clear. Now I want to raise a new one.

How does text-and-text live broadcast come true, just like the common online [text-and-text live broadcast of a new product launch]? What is a good design to deal with this high concurrency in a short time?

Alas ...... If you don't have millions of users, and you don't have millions of visits per second, it doesn't matter how the backend is tossed.
Adding a redis instance for caching is not a fundamental problem,ArchitectureIt can be clarified without a sentence or two.
The front-end implementation is nothing more than getting the latest data every 30 seconds or 10 seconds (custom.

You want to ask how to implement text-and-image live broadcast? Or how to achieve high concurrency?

One is the frontend and the other is the backend.