Demo Requirements

General requirements:

1. You must complete all elements of the demo during the 30-minute slot you have reserved. Points will be deducted if you are unable to complete all elements of the demo during that time, for example because you are not prepared at the beginning of the demo or because you arrive late.
2. You must demonstrate your program running on the microcloud.
3. You must demonstrate your program running on several different nodes. Each instance of the backend or frontend must run on a different microcloud node.

If you implemented strong consistency you must demonstrate the following:

1. Launch a primary and one secondary node
2. Launch at least two frontend nodes
3. Execute several POST and GET requests from each frontend
   1. Use logs or command line output to demonstrate communication between the primary and secondary
4. Lauch a second secondary node
   1. Use logs or command line output to demonstrate that the new secondary receives a correct copy of the database
5. Launch another frontend
6. Execute several more POST and GET requests from the frontends
7. Kill the primary node
   1. Use logs or command line output to demonstrate that the election algorithm works correctly
8. Execute several more POST and GET requests from the frontends
9. Demonstrate that if the primary fails after replicating to secondary 1 but before replicating to secondary 2 that the data store is made consistent after the new primary is elected

If you implemented eventual consistency you must demonstrate the following:

1. Launch two backend and two frontend nodes
2. Execute several POST and GET requests from each frontend
   1. Use logs or command line output to demonstrate gossiping between the backends
3. Use logs or command line output to demonstrate correct updating of the vector clocks
4. Launch a third backend node
   1. Use logs or command line output to demonstrate that the new backend receives a correct copy of the datastore
5. Execute several POST and GET requests from each frontend
   1. Use logs or command line output to demonstrate correct updating of the vector clocks
6. Kill one of the backend nodes
   1. Use logs or command line output to demonstrate that failure of the backend is discovered
7. Execute several GET and POST requests from each frontend
8. Demonstrate that if a frontend contact a backend with a GET and has a higher timestamp the backend will not reply with older data