Nuria added a comment.
> As mentioned, we might want to use a single node process exposing parsoid, > restbase & eventbus for small (third party) installs, but might as well use > the new EventLogging service in production. To date we do not have a third party install small use case but rather an internal production one (edit stream) so let's focus on this one and thus let's focus on adapting the EL change. > I don't see having two implementations of a simple service as a bad thing. I certainly disagree , I could see how we could have (for testing) a node mockup service for rest endpoint for -for example- a vagrant role, but I cannot see two full fledged systems doing the same thing as a positive outcome, rather it signals to me " duplication of effort" . > What we (=== Services team) have committed on doing this quarter is creating > the change propagation system which aims at replacing the (hacky) > RestbaseUpdateJobs extension. A A quaterly goal is not good for itself, it is a means to provide value to the organization. In this case duplicating efforts is producing technical debt and a lot of friction. TASK DETAIL https://phabricator.wikimedia.org/T114443 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Ottomata, Nuria Cc: Milimetric, RobLa-WMF, brion, intracer, Smalyshev, mark, MZMcBride, Krinkle, EBernhardson, bd808, Joe, dr0ptp4kt, madhuvishy, Nuria, ori, faidon, aaron, GWicke, mobrovac, Eevans, Ottomata, Matanya, Aklapper, JAllemandou, jkroll, Hardikj, Wikidata-bugs, Jdouglas, aude, Deskana, Manybubbles, daniel, Mbch331, Jay8g, Ltrlg, jeremyb, Legoktm _______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
