Glossary
Every term the courses use, defined in one line and then in a paragraph. Written to be read out of order.
Showing 6 of 124
Filling in historical data after adding a new column.
The step in a safe schema change where existing rows are given values for a newly added column. Usually done in batches so it does not lock the table or overwhelm the database.
Work done after the response is sent.
Work moved out of the request so the user is not left waiting: sending email, processing an upload, generating a report. Requires somewhere to report progress and somewhere to report failure.
How much damage a wrong action can do.
The scope of what a component can affect when it misbehaves. Read-only access has a small radius; the ability to delete records or send messages on your behalf has a large one. The primary control is not granting the capability at all.
See also Agent, Authorization
A message the receiving server refused.
A hard bounce means the address does not exist and never will; a soft bounce is temporary, such as a full mailbox. Sending again to a hard bounce is among the fastest ways to be judged a spammer, which is why providers keep a suppression list on your behalf.
See also Deliverability, Retry, Transactional email
A change that makes existing valid usage stop working.
Removing a field, renaming one, making an optional input required, or changing a type. The problem is that you often cannot fix it by deploying again, because the broken caller is a phone app or a script you do not control.
See also Versioning, Deprecation, Contract
Turning source code into something runnable.
Compiling, bundling and optimising your source into deployable output. A failed build is good news, because the pipeline caught a problem before any user did.