This RFC calls for a split of backend services between presentation on one side, and data storage and manipulation on the other. More here: https://www.mediawiki.org/wiki/Requests_for_comment/Service_split_along_presentation_vs_data_manipulation_line
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T88301 RFC: Clean frontend - backend separation; make all frontends API consumers | |||
| Declined | None | T89889 RFC: Service split along presentation vs data manipulation line |
This was discussed in yesterday's RFC office hours meeting. There's general support for the split, but RFC needs more details, especially on how PHP code (like special pages) calls backend services.
The RFC has seen no activity in a long time. It does not really make any concrete proposal Perhaps it could become a proposal for an architecture guideline, but then that proposed guideline would have to be written first. Or the RFC could propose an effort to refactor API modules, Special pages and Action classes to extract the application logic in a presentation-neutral manner.
Closing this RFC without current backing in favour of more active current proposals:
I've merged the external links from this task and mediawiki.org page to T111588.