Go & Vanilla JS: Fullstack Without Frameworks vs API Design in Node.js

Ten hours eleven minutes covering the full stack end-to-end: Go project setup and architecture, a JSON REST API with structured handlers, Postgres integration via a repository interface pattern, Vanilla JS web components, a client-side SPA router built from scratch, View Transitions API, search/filter/sort, and a complete JWT authentication flow covering registration, login, server-side middleware, and client-side route guards. Published May 27, 2025 — compatible with Go 1.22+ and modern browser APIs. The course deliberately avoids backend frameworks (no Gin, Echo, or Fiber), relying on Go's standard library, keeping outcomes transferable to any Go project.

Maximiliano Firtman is a prolific Frontend Masters instructor with prior courses on Mobile Web Development, Progressive Web Apps, and JavaScript Performance. The course holds a 4.9/5 star platform rating — among the highest for full-stack courses on Frontend Masters. Students consistently cite his habit of explaining architectural decisions and trade-offs rather than simply typing out code, and his willingness to debug real issues live during recording rather than presenting pre-cleaned output. Reviewers describe him as a "true master" whose teaching style emphasises the reasoning behind every decision.

Access requires a Frontend Masters subscription (~$39/month or ~$390/year for individuals) rather than a one-time purchase. Strong value for learners using the broader catalog — Frontend Masters covers JavaScript, TypeScript, React, CSS, Node.js, and dozens of related tracks under one subscription. Weaker for those taking only this course. No free tier beyond a short preview. The subscription cost is the dominant frustration across otherwise positive reviews, consistent with complaints across the entire Frontend Masters catalog.

The course builds a complete movie catalogue application end-to-end: a Go REST API with structured JSON handlers, a Postgres layer using a repository interface pattern, AIR-powered live-reload during development, full JWT authentication (registration, login, server-side middleware, golang-jwt token generation), and a Vanilla JS SPA with a hand-rolled client-side router, View Transitions, web components for every UI element, a search/filter/sort feature, and authenticated user pages (My Account, Favorites, Watchlist). Full authentication including client-side route guards distinguishes this course from most full-stack offerings that leave auth as an exercise or third-party library call.

The deliberate no-framework approach teaches patterns that transfer to any technology choice: the router is built from scratch, web components replace UI libraries, state management uses the Proxy pattern. Students report that this improves their ability to evaluate frameworks critically, because they understand what each framework is solving. Go's standard library — net/http, database/sql, log/slog — maps directly to production Go codebases. The Postgres repository pattern, AIR for live-reload, and Postman-tested API routes represent practices encountered in real engineering teams.

The current version (v5) is a roughly 10-hour, end-to-end build of a production REST API: Express routing and middleware, a Postgres database with migrations, JWT-based authentication and authorisation, TypeScript throughout, runtime schema validation with Zod, error handling and integration testing with Vitest, finishing with a deploy to Render. Reviewers repeatedly describe it as "comprehensive" and as covering "all the important backend topics" in a single coherent project. The one structural criticism, raised by a workshop attendee, is that the database-choice discussion (SQL vs NoSQL) arrives later than it should, and a few exercises bleed code meant for later steps into earlier ones.

Scott Moss — a senior engineer at Netflix and a two-time Y Combinator founder — is the most consistently praised element across our entire sample. Learners describe him as explaining "each and every concept and line of code in an easy-to-understand and easy-to-follow way," and one blogger notes his "super relaxed, but brilliant mad scientist vibe that makes learning feel comfortable." A reviewer of his related Node.js course calls his teaching "engaging and informative, making complex topics accessible to learners of all levels." No reviewer in our sample criticises his clarity; the only instruction-adjacent note is occasional ambiguity about where an exercise is meant to stop.

The course is not standalone-purchasable: it is included in a Frontend Masters subscription (monthly or annual), which also unlocks the entire catalogue including Scott Moss's other Node, Next.js and AI courses. Reviewers who already subscribe treat this course as one of the highest-value backend titles on the platform; one blogger who tried 20+ backend courses lists it among his top recommendations. The subscription model means it is excellent value for active learners but poor value for someone who wants only this one ~10-hour course and nothing else — there is no one-time purchase option.

There is no graded feedback, peer review or instructor marking — this is a recorded workshop, not a cohort course. What learners get instead is a well-structured GitHub repository with per-lesson branches and exercise solutions, which several reviewers single out as excellent for "quick lookups" and for checking their work. In-person workshop attendees got live Q&A, but on-demand viewers do not. The exercise-scope ambiguity noted by one reviewer ("it was often a little unclear where we were supposed to stop") is the main friction point in the self-check loop.

This is the course's strongest dimension. The stack it teaches — Express, Postgres, JWT, TypeScript, Zod, Vitest, deploy to Render — maps directly onto what working backend teams actually ship in 2026, and one reviewer explicitly notes the API design patterns "apply to Java, Python, Go, Node.js and other backend technologies," not just Node. Multiple learners report feeling "more confident about building APIs" and "what I'm doing in Node.js and TypeScript" immediately afterward. The production-deployment ending is the part reviewers most often credit for closing the gap between tutorial code and shippable code.