AtroposPHASE II DEMOSCOMP 415, Spring 2008

TABLE OF CONTENTS

1. System Control2. Correlation3. View Client4. Conclusion

SYSTEM CONTROL1. System Control2. Correlation3. View Client4. Conclusion

SYSTEM CONTROL

Start System Register Clients Assign Resources

INITIALIZE SYSTEM

Run instance of controller Start controller Run instance of data client

Attach parser to data clientMake direct API calls to send messages

Register data client with controller

CON

TROLLER U

ML DIAGRAM

Is a:

• IAdmin

• IRegistrar

Has a:

• IControllerState

REGISTER CLIENTS 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

REGISTER CLIENTS

ASSIGN RESOURCES

Data client needs to send messages to at least one correlation engine

May share this engine with another data clientDetermined by system graphMay also be distributed by load balancing logic

Data client is unaware of what the next step isExternal router(s)Co-located correlation engine (intra-server messages)

CORRELATION1. System Control2. Correlation3. View Client4. Conclusion

CORRELATION

FIX Parser Arbitrary Rules: FIX Upstream Units

VIEW CLIENT1. System Control2. Correlation3. View Client4. Conclusion

VIEW CLIENT

Graphical Interface Real-Time Updates Use Cases

VIEW CLIENT – USE CASES

View Server Latencies Update in Real Time Single Server View Path View Message Filtering

VIEW | W

IREFR

AMES

MULTIPLE SERVER VIEW

VIEW | W

IREFR

AMES

SINGLE SERVER VIEW

CONCLUSION1. System Control2. Correlation3. View Client4. Conclusion

CONCLUSION - SUMMARY

System Control Correlation View Client

AtroposCUT THROUGH THE TANGLED WEB…

Thank You For Listening!