Nuria added a comment. > a way to expose a stream of events in a defined format that can be consumed > easily by a range of clients.
This talks about consumption, not production but I do not want to get too deep into that cause I really I do not think we are discussing whether this is technically more sound or not. What I would like to emphasize is that we should think whether there are true users for the system we are building. Example: right now we have a concrete use case: search team is publishing events to kafka directly, we need a place so consumer and producer can have access to schemas, While we can glue a system that works, seems to me that the MVP needs to provide value on this space with our current use cases and needs. More so when the use case for the edit stream is analogous to search use case. Hopefully this makes sense. As I understand it, an MVP is a "product" whose criteria of success depends on how well it serves the use cases it is set to satisfy. > I also think that we should look at actual data before making assumptions > about latency. On my opinion performance concerns should be left aside until we know what are our functional goals. TASK DETAIL https://phabricator.wikimedia.org/T114443 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Nuria Cc: EBernhardson, bd808, Joe, dr0ptp4kt, madhuvishy, Nuria, ori, faidon, aaron, GWicke, mobrovac, Halfak, Eevans, Ottomata, Matanya, Aklapper, JAllemandou, jkroll, Smalyshev, Hardikj, Wikidata-bugs, Jdouglas, RobH, aude, Deskana, Manybubbles, mark, JanZerebecki, RobLa-WMF, fgiunchedi, Dzahn, jeremyb, chasemp, Krenair _______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
