Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
MediaWiki's service-oriented architecture (SOA) and what it means for SMW? #1170
 talks about service-oriented architecture (SOA) and the introductory text sounds as if installation of MW is becoming more difficult in future and would require mandatory external services to be installed in order to run a bare-bone MW.
@kghbln @JeroenDeDauw @ckoerner @hexmode Maybe a topic for the SMWCon on how this change (or requirement) would influence running Semantic MediaWiki (given its close dependency on MW) for users not running a server farm or a full IT environment.
Well, how would a service-oriented architecture (SOA) MW effect user in terms of:
What would be the benefit/cost for users (not of the size of WMF) to run MW with external services such as node.js, cassandra, or parsoid.
Why would I (as a user) need a VE/Parsoid with the burden to maintain such service (and keep them updated/alive) just to a have a fancy wiki-editor with a more appealing visual appearance?
Given the lack of response on inquiries  to help extension developers to integrate SMW and VE, or answer questions on how wikitext parsing  suppose to be integrated with Parsoid I'm hesitant to see a fruitful outcome in terms of VE integrability.
I'm not sure I'm the best person to talk about the SOA approach that MW
The best place to have this discussion is with Rob Lamphier and the MW
While the simpler, nostalgic past has meant that installing a wiki just
There are several objections to the SOA approach. Here are a few, but
To your specific point about node.js: PHP 7 is removing the primary
There was a really good presentation at Wikimania by Ed Sanders about
I have already been agitating for fewer services. The counter argument
That is a good thing, but there is no reason this sort of isolation
So, what does this all mean for SMW?
I think it is obvious that the status quo isn't going to work. For one
That means we need to get developers who are familiar with SMW to
Working with the architecture committee -- helping them understand the
Instead of pining for the past, we need to shape the future by making
Warning: not very constructive rant up ahead:
Services neither solve the existing coupling problems, nor are they required to achieve proper isolation in new code. Decisions such as "we will move MediaWiki towards SOA" come over to me like saying "we will now use this big hammer for all our upcoming construction work".
Gets a vote of non-confidence from my side based on what I've seen so far.