COMP 415, Spring 2008

T ABLE OF C ONTENTS 1. System Control 2. Correlation 3. View Client 4. Conclusion

S YSTEM C ONTROL 1. System Control 2. Correlation 3. View Client 4. Conclusion

S YSTEM C ONTROL Start System Register Clients Assign Resources

I NITIALIZE S YSTEM Run instance of controller Start controller Run instance of data client Attach parser to data client Make direct API calls to send messages Register data client with controller

C ONTROLLER UML D IAGRAM Is a: IAdmin IRegistrar Has a: IControllerState

R EGISTER C LIENTS Clients can find dynamically-located controllers Mule message is sent with registration data Controller tracks system graph Correlation engine instantiated Adapter is sent back to data client Correlation engine may reside on client’s machine Message may have to go through external router Controller knows about all pieces and can detect outages

R EGISTER C LIENTS

A SSIGN R ESOURCES Data client needs to send messages to at least one correlation engine May share this engine with another data client Determined by system graph May also be distributed by load balancing logic Data client is unaware of what the next step is External router(s) Co-located correlation engine (intra-server messages)

C ORRELATION 1. System Control 2. Correlation 3. View Client 4. Conclusion

C ORRELATION FIX Parser Arbitrary Rules: FIX Upstream Units

V IEW C LIENT 1. System Control 2. Correlation 3. View Client 4. Conclusion

V IEW C LIENT Graphical Interface Real-Time Updates Use Cases

V IEW C LIENT – U SE C ASES View Server Latencies Update in Real Time Single Server View Path View Message Filtering

V IEW | W IREFRAMES M ULTIPLE S ERVER V IEW

V IEW | W IREFRAMES S INGLE S ERVER V IEW

C ONCLUSION 1. System Control 2. Correlation 3. View Client 4. Conclusion

C ONCLUSION - SUMMARY System Control Correlation View Client

Thank You For Listening!