Confirmed users
1,927
edits
Auto-tools/Projects/Pulse: Difference between revisions
→Mozilla Pulse
| Line 5: | Line 5: | ||
Mozilla currently has a ton of different systems that are inter-connected via polling, screen scraping, email, and other brittle methods. To make their lives easier community members often build tools on top of this house of cards, adding yet another level of scraping and polling. Many systems don't even export important data for others to scrape and use, preventing better tools from being written. | Mozilla currently has a ton of different systems that are inter-connected via polling, screen scraping, email, and other brittle methods. To make their lives easier community members often build tools on top of this house of cards, adding yet another level of scraping and polling. Many systems don't even export important data for others to scrape and use, preventing better tools from being written. | ||
The goal of | The goal of Pulse is to eliminate polling and add visibility into all aspects of Mozilla and its systems. This allows more robust, dynamic, and informative tools. | ||
File bugs: https://bugzilla.mozilla.org/enter_bug.cgi?product=Webtools&component=Pulse | File bugs: https://bugzilla.mozilla.org/enter_bug.cgi?product=Webtools&component=Pulse | ||
=== System Description === | |||
Pulse isn't any one thing. At its heart, it is a RabbitMQ system with a particular configuration and a set of conventions for using it. Pulse follows the pub-sub pattern, in which publishers send messages to topic exchanges, and consumers create queues bound to these exchanges in order to subscribe to the publishers' messages. The [https://pypi.python.org/pypi/MozillaPulse mozillapulse] Python package provides classes for existing publishers, consumers, and messages so you can quickly build Pulse applications. | |||
=== Status === | === Status === | ||