Asynchronous client-side web apps: Client and Server Analogy
by Sarah Burgess
9/21/18

The Client is a composer, and the Server is the Manager of all the session musicians.  The session musicians are located all
around the world, and play every possible instrument.

The composer decides she wants a certain kind of music with certain instruments.  She sends an order (the url)  to the manager
in a letter (the Domain name) asking for smooth jazz musicians to play a song, ASAP.

The letter is delivered to the Manager’s office (the ISP) and the manager gets out his rolodex of musicians (DNS) and sends back
the phone number (IP Address) of the contact person for the worldwide list of session musicians for smooth jazz .

The Composer calls the number (IP address) of the contact person and asks for (sends a request) for a couple saxophone players,
a piano player, a jazz flute player, a singer, a drummer, a bass player, a rhythm guitarist, and a trumpet player.   The contact
person sends over the requested musicians (sends response) to the composer’s studio.

Then the composer decides they need a singer, a backup singer, and a xylophone player.  The composer calls back the Contact person
(IP address) and requests (sends request) those musicians.  The Contact person is like, “Sure, I got you” and sends over the requested
musicians (sends response).

The musicians arrive in time to start the song together, except for the bass player who walks in late but no one notices and he’s
able to sit in without missing a beat (asynchronous response).