Glossary · 75 terms
Software Architecture glossary
Every new word in the Software Architecture course, in plain English, explained on a card the first time it comes up.
A
- abort
- cancel a transaction so none of its changes are keptUnit: Patterns at scale
- analytics
- analysing data to answer business questions; analysts are the people who do itUnit: Distributed systems
- API call
- one request sent to an API, and the response it returnsUnit: Distributed systems
- at-least-once delivery
- the message system promises every message arrives, but some may arrive twiceUnit: Distributed systems
- atomic
- all-or-nothing: the steps happen together or not at all, and nothing can sneak in betweenUnit: Patterns at scale
- attacker
- a person deliberately trying to break into or misuse a systemUnit: Structure and styles
- audit log
- a permanent record of who did what and when, kept so it can be checked laterUnit: Architecture from zero
- authentication
- checking someone is who they claim to be, for example by password plus a codeUnit: Distributed systems
B
- back-of-the-envelope estimate
- quick, rough maths to find the order of magnitudeUnit: Distributed systems
- backend
- the server side of an app that stores data and does the work; the front end is what users seeUnit: Architecture from zero
- backup
- a copy of data kept so it can be restored after loss or damageUnit: Distributed systems
- billing
- working out and sending what each customer owesUnit: Architecture from zero
- browser
- the app used to open websites, like Chrome, Safari or FirefoxUnit: Architecture from zero
C
- cache stampede
- many requests miss the cache at once and all hit the database togetherUnit: Distributed systems
- codebase
- all the source code for a projectUnit: Structure and styles
- committed write
- a database change that has been fully saved and can no longer be lost or undoneUnit: Patterns at scale
- constraint
- a limit or rule the solution has to respectUnit: Structure and styles
- coordinator
- the node that runs a two-phase commit and decides commit or abortUnit: Patterns at scale
- CPU
- the main processor chip that runs a computer's programsUnit: Distributed systems
- CRUD
- create, read, update, delete: the four basic things an app does with stored recordsUnit: Patterns at scale
D
- database
- an organised store of data that programs can save to and look things up inUnit: Architecture from zero
- dependency
- something your work relies on, such as a library your code uses or a task that must finish firstUnit: Architecture from zero
- dependency inversion
- core code depends on an interface it owns, not on concrete detailsUnit: Structure and styles
- deploy
- to put a new version of software live where users can reach itUnit: Architecture from zero
- DNS
- the system that turns a name like example.com into an IP addressUnit: Architecture from zero
E
- egress
- data sent out of a cloud region or provider, usually charged per GBUnit: Patterns at scale
- encryption
- scrambling data so only someone with the right key can read itUnit: Architecture from zero
- event
- a message saying something happened, sent to whoever listensUnit: Structure and styles
- eventual consistency
- replicas may disagree for a while but end up the sameUnit: Distributed systems
F
- framework
- a ready-made structure to build on: a code framework, or a step-by-step method for thinkingUnit: Structure and styles
H
- HTTP status code
- a number in every reply: 2xx success, 4xx your request's fault (429 too many requests), 5xx server error (500)Unit: Checkpoint: Distributed systems
I
- index
- a sorted lookup structure that lets a database or search engine find items without reading everythingUnit: Architecture from zero
- IP address
- the number that identifies a machine on a networkUnit: Architecture from zero
J
- JSON
- a plain-text data format of {"key": value} pairs that programs exchangeUnit: Architecture from zero
L
- library
- ready-made code you add to your project instead of writing it yourselfUnit: Structure and styles
- linearizability
- the strongest consistency: every read sees the most recent writeUnit: Distributed systems
M
- merge
- to combine two things into one, like joining a code branch back into mainUnit: Structure and styles
- monitoring
- continuously watching a system's health using the data (telemetry) it reportsUnit: Checkpoint: Patterns at scale
N
- network partition
- a network fault that splits machines into groups that can't reach each otherUnit: Distributed systems
O
- OrderPlaced event
- a message announcing that a customer has placed an order, for any service that caresUnit: Distributed systems
- outage
- a period when a service is down or not workingUnit: Distributed systems
P
- Postgres (PostgreSQL)
- a popular open-source relational databaseUnit: Structure and styles
- production
- the live system real users use, as opposed to test copiesUnit: Structure and styles
Q
- quarantine
- set aside or isolate something so it can't affect the rest until it is checkedUnit: Patterns at scale
- query
- a question asked of a database or search systemUnit: Architecture from zero
R
- randomness
- chance: results that can differ each timeUnit: Distributed systems
- Redis
- a very fast in-memory data store, popular for caches, counters and queuesUnit: Distributed systems
- refactor
- restructure code without changing what it doesUnit: Checkpoint: Structure and styles
- replica
- one of several copies of the same data on different machinesUnit: Distributed systems
- retry with backoff
- try again after a failure, waiting longer each timeUnit: Structure and styles
- rollback
- going back to the previous working version after a bad changeUnit: Patterns at scale
- route
- to send traffic or requests to a particular placeUnit: Distributed systems
- row
- one record in a database table, such as one customer or one flightUnit: Architecture from zero
- RPC
- remote procedure call: calling a function that runs on another machineUnit: Structure and styles
S
- scheduled job
- a task that runs automatically at set times, such as a nightly job at 2 amUnit: Distributed systems
- schema
- a definition of the shape data must have: which fields, of what typeUnit: Checkpoint: Parts of a system
- script
- a small program that automates a taskUnit: Distributed systems
- sharding
- splitting one database's data across several machinesUnit: Distributed systems
- SLO
- service level objective: a target for how reliable a user journey should beUnit: Patterns at scale
- SOLID
- five principles for managing dependencies in code designUnit: Structure and styles
- sprint
- a fixed one-to-two-week work cycle in agile teamsUnit: Structure and styles
- SQL
- the standard language for asking a database questions and changing its dataUnit: Architecture from zero
- stale
- out of date; freshness is how recent data isUnit: Architecture from zero
- status code
- a number in every HTTP response saying how the request went, like 200 or 404Unit: Architecture from zero
- sync
- to coordinate or line up together; a sync meeting is one where people align liveUnit: Structure and styles
T
- table
- a grid of rows and columns in a database, like one spreadsheet tabUnit: Architecture from zero
- throughput
- how many requests a system handles per secondUnit: Architecture from zero
- throw an exception
- code stops normally and signals an error that a caller has to catchUnit: Patterns at scale
- trace id
- an id carried through every call of one request so its logs and spans connectUnit: Patterns at scale
- two-phase commit
- a protocol where a coordinator gets every participant to prepare, then tells all to commit or all to abortUnit: Patterns at scale
U
- unit cost
- spend divided by a business unit, such as cost per orderUnit: Patterns at scale
- uptime
- the share of time a service is working; downtime is when it isn'tUnit: Architecture from zero
- URL
- a web address, like https://example.com/orders/42Unit: Structure and styles
- UX (user experience)
- how using a product feels to a person, from clarity to speedUnit: Patterns at scale
V
- versioning and deprecation
- breaking changes ship as a new API version; the old one is deprecated (announced for removal) and kept for a whileUnit: Structure and styles
Your first Software Architecture lesson is five minutes away.
Not in the stores yet. Leave your email and we will tell you when it launches.