Software Architecture
4 filmsComing soonWhat happens, end to end, between your finger and the screen: the parts every app is built from, how they hand work to each other, and why one tap reaches many machines.
Every tap on your phone sets off a chain of machines that nobody has shown you. One part at a time, from your finger to the database and back, in plain words.
What happens, end to end, between your finger and the screen: the parts every app is built from, how they hand work to each other, and why one tap reaches many machines.
The near end of the map: what an app is made of, how one program asks another for something, what a request and a response carry, and how the app proves it is you on every tap.
What answers the request: what makes a computer a server, whether the back end is one program or many, how programs are packed to run anywhere, why companies rent their computers, and how new code reaches them.
Where an app keeps what it must not forget: what a database is, its two great families, how it finds one record among billions, how it never half-finishes a change, and where the big files go.
How one design serves a billion people: requests spread across many servers, answers kept close at hand, slow work done later, and one database split into many.
What keeps a system up while machines fail and code changes every day: spares that take over, watching it run, releasing changes to a few people first, testing changes on real users, and fitting an AI model in as one more part.