You need different TCP components because they must be retargetable. Partners can extend the architecture via replacing modules and server side scripting. Might have reached a limit in componentry. The humble stream still as legs. The component approach is best.
Context is hard - seems to be an optimization problem.
CM, management, alerts is a big resource sink. Need canonical approach to configuratiion and alerts. Guesses and beliefs. Product will die if it does not form a solid community. Not clear whose component problem it is in multi-component vendor environments.