FSWD · MERN Stack · The finale
You already own all four letters of MERN. This unit gives your server its formal vocabulary — REST — locks its order route behind JWT auth, surveys microservices, serverless and AWS, then connects both projects and deploys them to a real public URL.
Your 10 sessions, in order
No new folder this unit — that's the point. poshtik-campus-react/ (Lab 7) and poshtik-campus-server/ (Lab 10) both continue exactly where you left them: Lab 11 makes them finally talk to each other, and Lab 12 puts them both on the public internet.
The vocabulary for what your server has already been doing since Unit 4. What a web service is, provider and consumer, SOAP at survey depth, and REST — the style your entire Express API has been using, finally named formally.
SOONStatelessness, resources as nouns (/dishes, not /getDishes), the /api/all and /api/:id patterns the exam asks in real Express code, idempotency — and your /menu?category= route rewritten as /menu/:category, both shown side by side.
SOONYour whole Unit-4 API relabelled through REST's own vocabulary, API versioning, consuming an API with fetch() — Class 20's old preview finally fully realised — and CORS: the exact browser wall Lab 11 must climb before the two projects can talk.
SOONRight now anyone can POST /order as anyone. What a JWT is, its header-payload-signature anatomy decoded on a real token, a /login route issuing one, and Class 36's middleware stub grown into real auth protecting the order route.
SOONNo new fork — both folders, two terminals. The React Menu page fetches the real /menu from MongoDB instead of its local array, and the order form calls the JWT-protected POST /order, landing on a real OrderConfirmed screen. Four REST-API exam questions worked in full.
SOONYour server reviewed honestly as one monolith, what a microservice is, the trade-offs table (not "microservices are always better"), and the thought experiment: how Poshtik Campus could split into menu, orders and auth services — conceptually, not rebuilt.
SOONWhy pay for a server nobody's ordering from at 4 AM? What "serverless" honestly means, the AWS survey begins, Lambda as code that runs only when triggered — including a conceptual order-confirmation-notification Lambda tied to your own flow.
SOONEC2 as the always-on contrast to Lambda, five AWS services surveyed — S3, Lambda, EC2, RDS, API Gateway — where your dish photos could live on S3, the Free Tier's honest limits, and the AWS CLI installed for real. The unit's PYQ-densest class.
SOONlocalhost to public URL. Environment variables and why secrets never get committed, deployment proven first at room scale (a classmate's phone opening your LAN IP), then both projects' real cloud walkthroughs, rollback via the git habit you've had since Lab 1, and CI/CD basics.
SOONThe largest lab in the course, deliberately. Both projects deployed to real hosting, then the proof: a real order placed on the live site, traced login → JWT → MongoDB → confirmation screen, entirely on the public internet. Then one real feature upgrade, redeployed — and the whole-course recap.
SOONThe running project · no new fork — the payoff
Poshtik Campus పౌష్టిక్ క్యాంపస్ · both projects continue — and go live
The continuity that started with one HTML file in Lab 1 completes its arc here. Lab 11 rewires the React menu to fetch the real database-backed /menu and sends the order form through the JWT-protected POST /order to a genuine OrderConfirmed screen. Lab 12 deploys both halves and proves the same flow on a public URL — the order-confirmation journey, live, traced hop by hop.
/login route issuing JWTs, and auth middleware locking POST /order (Class 44)poshtik-campus-react/ can legally call poshtik-campus-server/ (Lab 11)OrderConfirmed component rendering the server's real confirmation response (Lab 11)npm run build (Lab 12)This exact trace — every hop watched in the Network tab, on the live site — is Lab 12's dedicated proof page, and the course's finish line.