As long as the sites size remains under, say, a few thousand simulataneous users per server, I think this approach will probably work okay if coded efficiently.  However, I still believe that to scale the true national service size companies like Twitter aspire to be, you need a tiered architecture with the subscriptions and routing handled in the messaging server. That server then feeds real-time track searching engines and the database which feeds the website.