On 26/03/2015 12:48, Renoir Boulanger wrote: > I have a question regarding fxa-notification-server and its design. > > It’s about the expected behavior in relation to message handling and the > subsystem it will work with. > > Will this component enforce the requirement of order over the guarantee > of reception?
The short answer is: we haven't discussed that in any depth. We have of course been *thinking* about it and the question will eventually come up. But requirements are not firm enough for us to commit to any particular guarantees. For our initial use-cases ordering is not terribly important, and we won't be deploying in a particularly distributed-systems fashion. As we get more experience with using the system and the APIs, we can iterate to lock down some more. I suspect we'll either wind up with something similar to NSQ (favoring availability and weakening ordering) or something similar to Apache Kafka (favoring strong ordering over availability). We'll certainly avoid trying to invent our own things somewhere in between! > I ask this because after reading the EPIC > mozilla/fxa-notification=server#4 [1] and looking at the code, I wonder > what MQ will be supported and the design decisions for the first release. > > On the WebPlatform Project, we are considering to deploy a message queue > system using [NSQ](http://nsq.io/overview/features_and_guarantees.html) > which allows "horizontal scale". The NSQ project says its designed in a > way that you can add nodes and, it takes care by itself to detect peers > without configuration changes. Cool, if you've got a concrete use-case in mind for a notification service, please share and we can discuss it here. It's definitely the right time to get in early and have your needs considered. Cheers, Ryan _______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
