Output:1.3: Difference between revisions
From atwg
(Created page with "{{Output |Description=Refactored RESTBase |Parent Outcome=Outcome:1 }}") |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Output | {{Output | ||
|Description= | |Description=refactored RESTBase | ||
|Parent Outcome=Outcome:1 | |Parent Outcome=Outcome:1 | ||
}} | }} | ||
Revision as of 14:02, 9 February 2018
| Output | refactored RESTBase |
|---|---|
| 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 |
| Task | Description | Depends On Tasks | Type | Associated Outputs | Primary Team | Collaborating Teams | Start Year | Duration | Risks | Contingencies | Benefits | Assumptions | Implications | Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Simplify the RESTBase stack | Separate the routing and storage components of RESTBase into two services | Development | Output 1.3 | Services | 0 | 3 | ||||||||
| Create a multi-purpose key/value storage component | Profiting from the RESTBase split, create a multi-DC storage component that can serve multiple needs inside Wikimedia's production environment. Use cases include, but are not limited to, Parsoid storage, MCS and others. | Simplify the RESTBase stack | Output 1.3 | Services | 1 | 3 | ||||||||
| Isolate session data by creating a specialised session service | Create a session storage service that uses the storage component and isolate it from the rest of the system using a simple API, and make it easily available from MediaWiki | Create a multi-purpose key/value storage component | Output 1.3 | Services | MediaWiki Platform | 0 | 3 |
