Max number of components
I have an application is that is made of up of 140-200 what they call projects. Each on it's own release cycle. The application will pick and choose different project versions to make up the application. This seems like a case for having each project be represented as a component. Would a stream with 150 components be unreasonable?
Accepted answer
Starting with 6.0, the availability of hierarchical components should allow you to work effectively with a much greater number of components than in previous releases. There is still work to be done, but the goal is to make it feasible to have hundreds, and eventually, thousands, of components in a single stream/workspace.