Start here: putting it all together

You now know the pieces: how identity is proved, how tokens are made and kept safe, and how policy decides who may do what. This last track puts the pieces together. It teaches no new mechanism. It teaches you to design with what you know, for products you can picture: a school-fees app, a food-delivery startup, a clinic system and a big sale day.

What this track gives you

An architect makes choices, and every choice has a cost. Where should an app keep its tokens? How long should a token live? Should you build login yourself? None of these has one right answer. You learn to weigh the options. Most labs here are small games: you make the call, then see what it costs.

The journey

First you place tokens. Where do they live in a browser (the BFF)? How does identity travel between services? Then you keep customers (tenants) apart and set how long tokens live. Last come two big decisions: build or buy, and what to do when your IdP (the sign-in service) goes down.

1. Where tokens live & the BFF — a school-fees app keeps tokens out of the browser, behind a small server.
2. Identity across microservices — one food order crosses four services. Check the user once, then pass trust on, hop by hop.
3. Multi-tenancy isolation — a clinic system keeps each clinic's data apart: silo, pool or bridge.
4. Token lifetimes — a shopping app balances a thief's window against Maya's patience.
5. Build vs buy — a food-delivery startup decides who builds the login.
6. When your IdP goes down — the sale-day outage: keep working, fail over, keep an emergency door.
7. The big picture — all the calls on one board.
8. Cheat sheet & pop quiz — the track on one page, then five scenarios.

How to use it

Take one lesson at a time. Your progress saves in your browser, and you need no account. Most lessons end with a lab where you make the call yourself. The Final Exam and your certificate come after the last lesson, and the last page shows what to do next.

Start with where tokens live and the BFF.