Compiler Support for Distributed Systems

1. Compiler Support for Distributed Systems Martin C. Rinard University of California, Santa Barbara

2. Goal Provide Software Tools That Support Development of Components of Distributed Systems • Problems • Interoperability • Distributed Component Development • Components Developed At Different Times • Components Developed By Different Organizations • Interaction With People • Our Approach • Formal Interface Definitions Using Finite State Machines • Automated Interface Extraction, Verification and Testing • Novel Constructs for Building Robust User Interfaces

3. Model of Computation • Distributed Systems Built Out Of Components • Processes • Agents • Objects • Components Communicate Via Message Passing • Asynchronous Sends, In Order Delivery • send(component, message type, parameters) • Blocking Receives • recv(component?, message type, parameters?) • Selection Construct

4. 1 2 3 4 5 6 7 8 9 0 . Example Customer ATM Machine Bank Please Deposit $5,000,000.00

5. Scenario • Existing ATM System • Bank Contracts For New Kind of ATM • New ATM Must Interoperate With Existing Bank Software • ATM Developer Must Know Bank Interface • Bank Unwilling to Release Source Code

6. Bank Implementation loop { select { recv(atm?, DEPOSIT,account?,amount?) -> { account.balance += amount; send(atm, OK); } recv(atm?,WITHDRAW,account?,amount?) -> { if (amount < account.balance) { account.balance -= amount; send(atm, OK); } else { send(atm, FAILED); } } }}

7. recv(atm?,DEPOSIT) recv(atm?,WITHDRAW) send(atm,OK) send(atm,FAILED) send(atm,OK) Bank Interface • Message Type Information • recv(component?, DEPOSIT, int?, int?) • recv(component?,WITHDRAW, int, int) • send(component, OK); • send(component, FAILED); • Message Sequencing Information

8. Conformance of Components and Interfaces • Context • Have A Component (Bank Component) • Have An Interface (Bank Interface) • Does Component Correctly Implement Interface? • Analyze Program To Automatically Extract New Interface • Abstract Away From Computation • Translate Communication and Relevant Flow of Control Constructs Into Parts Of Finite State Machine • Does Extracted Interface Conform to Original Interface?

9. Automatic Interface Extraction • Individual Programming Constructs • if (exp) { send(c,OK); } else { send(c,FAILED); } • select { recv(c?, OK) -> {} recv(c?, FAILED) ->{} } • Interprocedural Interface Extraction Internal Choice send(c,OK); send(c,FAILED); External Choice recv(c?,OK) recv(c?,FAILED)

10. Basic Conformance Concepts • Concept Of Conformance • An Interface I Extracted From a Component • An Interface J That System Is Designed to Use • If I Conforms to J, Can Safely Use Component In System • If Every Message Sent Is Received With J, Every Message Sent Will Be Received With Component • A State S is Stable If It Is Not An Internal Choice Point • A State S is Receptive If It Can Only Receive Messages • Given Two Interfaces, Sets Of Corresponding States • Maximal Sets Of States Accessible Via Same Sequence of Sends and/or Receives

11. Original Interface Corresponding Sets In Example Extracted Interface recv(atm?,DEPOSIT) recv(atm?,WITHDRAW) send(atm,OK) send(atm,OK) send(atm,FAILED) recv(atm?,DEPOSIT) recv(atm?,WITHDRAW) send(atm,OK) send(atm,FAILED) send(atm,OK)

12. First Conformance Condition For Each Corresponding Set Of States Messages Sent From States In Extracted Interface Must Be A Subset of Messages Sent From States In Original Interface Extracted Interface Original Interface send(c,OK) send(c,FAILED) send(c,OK)

13. Second Conformance Condition For Each Corresponding Set Of States Messages Received In States In Extracted Interface Must Be A Subset of Messages Received In States In Original Interface Original Interface Extracted Interface recv(c?,OK) recv(c?,FAILED) recv(c?,OK)

14. recv(c?,MSG) recv(c?,OK) Third Conformance Condition For Each Corresponding Set Of States If Receptive States Of Original Interface Must Receive One Of A Set Of Messages, Receptive States Of The Extracted Interface Must Also Receive One Of That Set Of Messages Original Interface Extracted Interface recv(c?,OK) recv(c?,OK)

15. Final Conformance Conditions For Each Corresponding Set Of States • If Original Interface Always Sends A Message • Extracted Interface Must Always Send A Message • If Original Interface Always Reaches A Receptive State • Extracted Interface Must Always Reach A Receptive State • If Original Interface Always Reaches A Stable State • Extracted Interface Must Always Reach A Stable State

16. Original Interface Does Extracted Interface Conform To Original Interface? Extracted Interface recv(atm?,DEPOSIT) recv(atm?,WITHDRAW) send(atm,OK) send(atm,OK) send(atm,FAILED) recv(atm?,DEPOSIT) recv(atm?,WITHDRAW) send(atm,OK) send(atm,FAILED) send(atm,OK)

17. Implementing ATM • Interface Between Customer and Bank • Model Customer As Simply Another Component • Customer Actions Modeled As Message Sends • Physical Actions Translate Directly Into Message Sends • Example • Customer Pushes the Deposit Button • System Internally Generates send(atm, DEPOSIT) • Customer Hits 8 Digit On Keypad • System Internally Generates send(atm, DIGIT, 8)

18. ATM Primitives void get_amount(int * amount) { *amount = 0; loop { select { recv(DIGIT,&d) -> { *amount = (*amount * 10) + d; } recv(DONE) -> break; } } }

19. ATM Implementation loop { get_account(&account); select { recv(DEPOSIT) -> { get_amount(&amount); send(bank,DEPOSIT, account, amount); recv(bank?, OK)-> { Confirm Deposit } } recv(WITHDRAW) -> { get_amount(&amount); send(bank, WITHDRAW, account, amount); select { recv(bank?,OK) -> { Dispense Cash } recv(bank?, FAILED) -> { Generate Error Message } } } }}

20. ATM Message Type Information • User Actions • recv(DEPOSIT) • recv(WITHDRAW) • recv(DIGIT, int?) • recv(DONE) • Sends To and Receives From Bank • send(bank, DEPOSIT, int, int) • send(bank, WITHDRAW, int, int) • recv(component?, OK) • recv(component?, FAILED)

21. ATM Message Sequence Information recv(FAILED) recv(DIGIT) recv(DONE) recv(OK) recv(OK) recv(DEPOSIT) recv(WITHDRAW) recv(DIGIT) recv(DIGIT) recv(DONE) recv(DONE) send(bank,DEPOSIT) send(bank,WITHDRAW)

22. Automated Testing And Verification • Compose Interfaces • Simulate to Derive All Possible System States • Flag Potentially Erroneous States • A Message Sent But Never Will Be Received • User Messages Treated Specially • Any Sequence of User Actions Possible • User Actions Processed Only In Quiescent System States

23. Simulation Reveals Potential Problem In Example • Customer May Back Out of Transaction • Customer Starts A Deposit • System Expects to Input Amount to Deposit • But Customer Hits Withdrawl Button • System Does Not Handle Event • Programming Mismatch • Programmers Reason With Expected Sequences, But • Program Must Correctly Handle Exceptional Sequences • Standard Constructs Do Not Support Construction of Robust User Interfaces

24. A Construct For Building Robust User Interfaces • Goals • Preserve Ability To Reason With Expected Sequences • Easily Augment Program For Exceptional Sequences • Reseting Select Construct • Same Syntax As Select • Same Behavior As Select For Expected Sequences • Unselected Receive Alternatives Stay Enabled • If Customer Generates Exceptional Action • Implementation Resets Active Alternative • Starts Newly Selected Alternative • Reset Actions - Executed When Alternative is Reset

25. Reseting Select Construct resetSelect { recv(DEPOSIT) -> { get_amount(&amount); send(bank,DEPOSIT, account, amount); recv(bank?, OK)-> { Confirm Deposit } } recv(WITHDRAW) -> { get_amount(&amount); send(bank, WITHDRAW, account, amount); select { recv(bank?,OK) -> { Dispense Cash } recv(bank?, FAILED) -> { Generate Error Message } } } recv(DIGIT,d?) -> { Print Error Message } recv(DONE) -> { Print Error Message }

26. Comparison With Standard Methods • Event Loop • loop { wait_event(&e); process_event(e); } • System State Encoded in Global Variables • Demultiplexing Required To Determine Correct Action • Difficult To Determine if All Events Handled Correctly • Proposed Approach • Supports Use of Standard Program Constructs • Standard Flow of Control, Local State • Semantically Related Code Appears Together • Easy To Write Programs That Handle Events Correctly • Easy To Determine if All Events Handled Correctly

27. Conclusion • Program Analysis Techniques Can Help Programmers Develop Robust Distributed Systems • Include Sequencing Information in Interface • Automatic Interface Extraction • Automatic Verification of Interoperability • Interaction With User • Model User As Another Component • Novel Construct For Robust User Interfaces

28. Potential Scenarios • System Developed From Scratch • Developer of ATM Software Needs to Know • Bank Interface • Reasonable User Interface • Bank Software Developer Needs to Know ATM Interface • Bank Contracts For A New Kind of ATM • New ATM Will Interact With Existing Bank Software • ATM Software Developer Needs to Know Bank Interface • Bank Unwilling Release Source Code

29. ATM Message Sequence Information get_account recv(DEPOSIT) recv(WITHDRAW) recv(OK) get_amount get_amount send(bank,DEPOSIT) recv(OK) send(bank,WITHDRAW) recv(FAILED)

30. Interface Uses • Documentation During Development • To Test That Components Correctly Implement Interfaces • Analyze Program to Automatically Extract Interface • Test if Interfaces Are Equivalent • To Drive Automated Testing and Verification • Compose Components • Simulate to Derive All Possible System States • Flag Potentially Erroneous States • User Messages Treated Differently • Any Sequence of User Actions Possible • User Actions Processed Only In Quiescent States