Loading…
While this loads — worth knowing
ElastiCache RedisnotElastiCache Memcached
Redis has data structures — sorted sets, counters, pub/sub. Memcached has plain keys and nothing else.
Loading…
While this loads — worth knowing
Redis has data structures — sorted sets, counters, pub/sub. Memcached has plain keys and nothing else.
Architecture pattern
when the front end is files, not a server
A single-page app is a bundle of files. Nothing has to run to serve them, so nothing should. S3 holds the objects, CloudFront copies them to edge locations near each viewer, and there is no instance to patch or scale.
In the order a request or a record moves through it. Each one links to the page that explains it.
Phrases that, when you meet them in a scenario, mean this shape rather than another. They are the tell, and they are what an exam question is built around.
Anything that has to be computed per request needs a second path — usually an API alongside, not instead.
Every shape has one. A design decision with no stated downside is usually a decision nobody has finished making.
These run through some of the same services, which is exactly why a brief that fits one can look like it fits another.
Reading a shape and producing one from a scenario that never names a service are different skills, and the exam asks for the second. The scenarios give you the brief; you draw the architecture and it is scored against what the brief requires.