Scalability.

I haven't performance-tested the Statuses module for D7, but I know from experience that the D6 version can handle sites with 50,000 users. Statuses are actually significantly lighter-weight than nodes by design. There are two main differences to be aware of: first, people tend to create 2-5 times more status updates than nodes, so you may have a lot of database records after awhile; and second, because people create status updates relatively quickly, caching becomes less effective. Other than that though there's generally less overhead to perform status-related operations compared to nodes.

You can certainly run a site using statuses as the main type of content. I know other sites do this.

Very interesting option.
However, as I see at the first glance, there is no Archive or paging mechanism. How to organize a site based on streams?

@AndrzejG, please keep each issue to only one topic.

However, the answer is that you can really customize it however you want. There's no archive view out of the box, but since Statuses integrates with Views, it is very easy to create one. (And the default streams do having paging, although some people choose to use alternative views paging systems to achieve for example an infinite stream like Twitter's.)

Hello,

do you have performance-tested the Statuses module in the meantime?

What is your assessment of the performance when several thousand users simultaneously read data from the statuses table and write data into the database table?

Has anyone experiences with this issue?

Thank you very much and happy Easter