|
|
| (2 intermediate revisions by one other user not shown) |
| Line 1: |
Line 1: |
| − | __NOTOC__
| |
| − | Note: This page is to share architectural information of Synaps temporarily. When the Synaps is open sourced, this page will be moved into its documentation page.
| |
| | | | |
| − | == Synaps Architecture ==
| + | Note: This page is moved to http://spcs.github.com/synaps |
| − | Synaps API is frontend of the system. It uses RabbitMQ for asynchronous processing. The messages are passed to Synaps Strom.
| |
| − | | |
| − | Synaps Storm is a topology implementation which is aimed to run on the Twitter Storm, real-time distributed stream processing system. Synaps Storm is based on the message driven architecture. Most of the messages are came from RabbitMQ. It notifies using Notification Queue so that other notification system can interoperate with the queue.
| |
| − | | |
| − | Both Synaps API and Synaps Storm use Cassandra no-sql database to store persistent data.
| |
| − | | |
| − | Following is Architecture of Synaps.
| |
| − | | |
| − | [[Image:Synaps$$Architecture$SynapsSystemOverview.jpg]]
| |
| − | | |
| − | following is an example of an integrated system.
| |
| − | | |
| − | Externally, Synaps interoperates with agents which inputs metric data periodically, such as VMMON which can get information from VM Hyperisor. Synaps Notification is a program that can send E-mail, SMS.
| |
| − | | |
| − | [[Image:Synaps$$Architecture$IntegratedSystemOverview.jpg]]
| |
| − | | |
| − | following is an example of deployment.
| |
| − | | |
| − | [[Image:Synaps$$Architecture$SynapsDeployment.jpg]]
| |
Latest revision as of 23:31, 17 February 2013
Note: This page is moved to http://spcs.github.com/synaps
