← कोर्सच्या मुख्य पानाकडे परत

🗓️ अभ्यास योजना — 12 धडे, 4 आठवडे

~3 sessions a week: read the lesson (~15 min) + run and change its section of arch/demo.py (~25 min). Tick lessons off — progress is saved in this browser.

🐢 स्थिर: आठवड्याला 3 सत्रे → 4 आठवड्यांत पूर्ण.
🐇 वेगवान: प्रत्येक भागासाठी एक weekend → 3 weekends मध्ये पूर्ण.
💰 खर्च: शून्य. तुमच्या लॅपटॉपवर Python 3.
0 / 12

WEEK 1 🧱 Rooms and corridors

What architecture is, modularity, layers. Lab: find the biggest blast radius; remove corridors and watch I and D move; try other floor orders.

~40 मि.
~40 मि.
~35 मि.
🏁 Checkpoint: you can say which decisions are expensive and read Ca, Ce, I and D for a component.

WEEK 2 ⬡ The core and its departments

Ports and adapters, DDD, styles. Lab: import the shipped sample and see the cycle fail; list the cross-department corridors; change the hop cost.

~45 मि.
~40 मि.
~40 मि.
🏁 Checkpoint: you can explain the dependency rule and why a modular monolith comes first.

WEEK 3 📌 Notices, cupboards, inspectors

Events and CQRS, data ownership, fitness functions. Lab: add a listener; change the lag and the outage; plant a Friday shortcut and watch the check fail.

~40 मि.
~35 मि.
~40 मि.
🏁 Checkpoint: you can choose between shared DB, API and events, and write an architecture test.

WEEK 4 🗺️ Drawings, logbooks, growth

C4, ADRs and trade-offs, evolution. Lab: render the DSL; change a weight until the winner flips; move routes in a different order.

~40 मि.
~35 मि.
~45 मि.
🏁 Checkpoint: 🏆 Capstone: point scan() at a real codebase you know: measure its floors, list its cycles, write two fitness functions and one ADR, and draw its C4 component view from the imports.

🎓 12 / 12 — the floor plan holds!

Next: the System Design school designs distributed systems, the Distributed Systems school explains what fails between machines, and the School portal has the rest.