Glossary
Every term the courses use, defined in one line and then in a paragraph. Written to be read out of order.
Showing 4 of 124
Signing in via another provider.
The user authenticates with Google or GitHub, who then tell your app who they are. You never see the password, so you cannot leak it. Has enough subtle failure modes that you should always use a library.
See also Authentication, Identity provider, Token
Being able to tell what your system is doing.
The combination of logs, metrics and traces that lets you answer questions about a running system, including questions you did not anticipate when you built it.
Showing the result before it is confirmed.
Updating the screen immediately on the assumption the request will succeed, reverting if it does not. Right for likes and checkboxes, wrong for payments and deletions. The revert path is the one nobody tests.
See also Pending state, Rollback
A scheduled job starting before the last one finished.
An hourly job that takes seventy minutes will have two copies running. Whether that is harmless or catastrophic depends entirely on what the job does.
See also Cron, Scheduled job