Congratulations
Suggest an editThe lessons took the principles one at a time, but a real system uses several of them in one feature. Take a single request to a public web API. Every part of it appeared in this course.
- TCP delivers the bytes reliably and in order and never reads them, which is the Irrelevance Principle.
- A few heavily reviewed certificate authorities vouch that the site is who it claims to be, which is the singleton.
- The HTTP request carries everything the server needs to answer it, so any copy of the service can take it, which is stateless design.
- The response comes back as JSON, because an outside developer who can open it and read it is unstuck in minutes, which is a tradeoff decided by the parent goal.
Each of the four is there because it answered a particular constraint, and each has a price that its lesson names. A compromised certificate authority exposes a large slice of the web, and a stateless server has to verify what the caller brings.
What to do with it
Pick a system you work on and read it the same way. Find the smallest part that touches the valuable data, then the one shared component everything else depends on, then what each component remembers between calls. Finally, take one operation the system exposes and ask what an informed, self-interested caller would do with it.
In your own designs, write down the constraint first. A principle applied only because you learned it adds complexity. A singleton that gets no more review than the fifty copies it replaced is a single point of failure.