Property:Notes
From atwg
0
Routing for external services should be handled outside of MediaWiki (Varnish). The MW routing should be done using a service runner that can be run separately from MW for WMF use, but could be run in the same process for small installs. Where a service lives, node, MW, or elsewhere should be transparent to clients. We should then figure out any necessary routing, mapping, proxying, etc without the clients needing to worry about this. This means we have an agreed upon REST url pattern that spans all services and routers. For MW APIs, thsse should be routed from Varnish to MW via some sort of configuration. +
Should be designed by a group consisting of members from the MW Platform team, Services, Readers and Contributors. This ensures that those who know the MW platform best, those who have experience designing REST services, and those who implement the clients all agree on the design +
CSA: Added "re-evaluate technology tradeoffs"; perhaps split into a separate first-year research goal? +
Refactor MediaWiki Core into well encapsulated components, removing global state and circular dependencies between classes +
Primary candidates are those where LAMP stack needs are vastly different than WMF scaling needs such as: Storage and Event Propagation +
The code cleanup and refactoring doesn't need to depend on the architecture document. +
Virtualization/Containerization/Cloud/Shared/Bare metal? +
These goals need to better stress "increase commonality between WMF and 3rd party installs", rather than treating 3rd party installs as a separate configuration target +
Improve installation of default MediaWiki for WMF development, testing and production environments as well as 3rd parties (ARCHIVED) +
I don't think we have full consensus on single-process LAMP vs node js helpers etc. +
