How systems talk
How one program asks another for something, and what it does while it waits.
Stop 1, next
One asks, one answers client and server
Think of it when a screen shows data that lives on another computer, or you wonder where a piece of code actually runs.
StartAbout 3 minutes. The word for it comes at the end.Stop 2, next
Think of it when one program needs something from another, or you are about to change what a program accepts or returns.
StartAbout 3 minutes. The word for it comes at the end.Stop 3, next
Shared rules for talking protocol, HTTP
Think of it when two programs that each work cannot understand each other, or you decide how a program reports an error.
StartAbout 3 minutes. The word for it comes at the end.Stop 4, next
Think of it when a site works for some people and not others after a move, or a new web address does not open yet.
StartAbout 3 minutes. The word for it comes at the end.Stop 5, next
Wait, or carry on sync vs async
Think of it when a screen freezes while it waits, a page makes its requests one after another, or a slow job sits between a user and the page they want.
StartAbout 3 minutes. The word for it comes at the end.Stop 6, next
A line of jobs queue
Think of it when work arrives faster than it can be done, or a slow job should not hold up the person who asked for it.
StartAbout 3 minutes. The word for it comes at the end.Stop 7, next
Who you are, what you may do authentication, authorization
Think of it when a request reads or changes data, and you must know who sent it and whether they are allowed.
StartAbout 3 minutes. The word for it comes at the end.