Output:1.1

Output	architecture for the flow of control and information from the user down to the database and back
Parent Outcome	Infrastructure for Wikimedia projects can be more easily scaled due to increased modularization, re-use, maintainability, and testability of the technology stack
Primary Team
Collaborating Teams	TechCom, MediaWiki Platform, Services, Performance, Parsing, Reading Infrastructure

Task	Description	Depends On Tasks	Type	Associated Outputs	Primary Team	Collaborating Teams	Start Year	Duration	Risks	Contingencies	Benefits	Assumptions	Implications	Notes
Research architecture requirements and needs, identify and resolve trade-offs	Starting from user stories and work flows, identify requirements. Based on available technology and resources, identify constraints. Present trade-offs to PMs and C-Level management for resolution. NOTE: This informs the re-design and refactoring of the API layer, MW core, as well as auxilliary aspects such as Varnish, RESTbase, and EventBus.		Research	Output 1.1	MediaWiki Platform	Services, TechCom, WMDE, Reading Infrastructure, Performance, Parsing	0	3
Write Architecture Spec		Research architecture requirements and needs, identify and resolve trade-offs	Documentation	Output 1.1	MediaWiki Platform	TechCom, WMDE	0