Distributed Pub Sub Event System Version 2.1

Rating:        Based on 1 rating
Reviewed:  1 review
Downloads: 6146
Released: Dec 16, 2011
Updated: Jul 28, 2012 by keithh
Dev status: Stable Help Icon

Recommended Download

Documentation WSP Event System Whitepaper
documentation, 650K, uploaded Jul 28, 2012 - 3208 downloads

Other Available Downloads

Application x86 Debug Setup
application, 1177K, uploaded Dec 17, 2011 - 405 downloads
Application x86 Release Setup
application, 776K, uploaded Dec 17, 2011 - 468 downloads
Application x64 Debug Setup
application, 1670K, uploaded Dec 17, 2011 - 352 downloads
Application x64 Release Setup
application, 828K, uploaded Dec 17, 2011 - 474 downloads
Documentation Installation Instructions for Data Centers
documentation, 24K, uploaded Dec 20, 2011 - 894 downloads
Documentation WSP Event System Overview
documentation, 670K, uploaded Jul 28, 2012 - 345 downloads

Release Notes


You need to install the Microsoft Visual C++ 2010 Redistributable Package. You can find it at:
x64 http://www.microsoft.com/download/en/details.aspx?id=14632
x86 http://www.microsoft.com/download/en/details.aspx?id=5555

Latest Enhancement

I added WspCommand to the event system. The main reason is the difficulty to collect real-time system information from servers. As an example, with the Wsp command functionality, it is now feasible to send a command to 8,000+ servers to get file version information of a specific file and get all responses back and process them within a couple of seconds. When we see performance issues in the eco-system, we can now collect real-time forensics from many or all servers to quickly find the state on the servers.

Creating commands is extensible. You would use the new CommandRequest and CommandResponse classes. To see an example of how to use the classes, you can look at the WspCommand sample application.

2.1 Enhancements

Many enhancements and bug fixes have been made to v2.1. In particular, it scales better and works across the WAN better. You now manage the config file for all machines at the origin server which is the top-most node in the hierarchy. In MSN, each data center has one or more parent routers which connect to the origin router. The client servers connect to the same name regardless of data center and the DNS resolves the name to a router in their same data center.

Logging now serializes events to JSON format.

To improve WAN communication, you can now specify how many socket connections a server has to its parent.

The whitepaper below is a out of date but close enough. The overview of the system is still mostly accurate.

I will add a deployment document in the near future to explain how to deploy and what arguments can be passed to the msi. Essentially, you set up your origin router and then all the other deployments you do will point to the origin router to get their config file. If someone really needs it sooner, let me know.

Reviews for this release

Amazing system. I'm surprised to find such solution for free. Great work!
by kostrse on Feb 14, 2011 at 12:45 PM