Our Stacks Explained 🖥️ 💪

Episode Summary

Executive Summary: The episode is a deep dive into the hosts’ custom course platforms and the technical decisions behind them: back-end frameworks, databases, front-end stacks, asset hosting, email delivery, hosting, testing, and APIs. Both emphasize building bespoke systems to handle course sales, access control, affiliate payouts, and content delivery at scale, while balancing flexibility, performance, and maintainability.

Main Topics: Why they built custom course platforms: Both hosts explain that off-the-shelf platforms couldn’t handle their mixed content models, multiple domains, affiliate systems, access rules, and automation needs, so they built custom stacks tailored to their businesses. Back-end architecture and framework choices: Scott describes using Meteor for tight front-end/back-end integration and built-in accounts, while Wes details his Node/Express stack with Passport for sessions and login flows. Both value control and rapid iteration. Data storage, database tooling, and administration: They both use MongoDB and discuss how their admin workflows evolved from manually editing data to creating robust internal tools for managing products, users, purchases, and reports. Front-end implementation and UI state management: The episode compares React-based interfaces, legacy jQuery/templated pages, styled-components, Stylus, session variables, and minimal state management, with both hosts preferring the simplest tools that fit the problem. Asset hosting, video delivery, and CDN strategy: They cover their approaches to hosting large files and video at scale, including S3, Backblaze B2, Vimeo, YouTube, CloudFront, Cloudinary, and the tradeoffs of bandwidth, speed, and global performance. Email infrastructure and deliverability: They discuss SMTP-based email pipelines, Mandrill, Postmark, Nodemailer, and HTML email tooling, highlighting deliverability, link tracking, and vendor lock-in risks. Testing, hosting, and operational maintenance: The hosts compare Mocha/Jest and Meteor test tooling, then discuss hosting on DigitalOcean, Galaxy, Heroku, and newer deployment models that reduce server maintenance and downtime.

Key Arguments: Custom systems are justified when products, permissions, and content models are specialized enough that generic platforms become restrictive. Meteor’s integrated model reduces friction for certain apps because the client and server communicate smoothly and accounts are built in, but the same flexibility can be achieved with a Node/Express stack. MongoDB works well for their use cases because the data is not heavily relational and both platforms benefit from flexible document structures. Internal admin tools are critical for running a content business efficiently; they reduce manual support work and enable better reporting and control. Keeping checkout friction low matters: requiring account creation too early can hurt conversions, but tying purchases to accounts later can create receipt and access issues. Hosting and bandwidth costs can become a major business expense, so using the right CDN/storage/video platform and compressing assets properly has large financial impact. Email providers should be chosen for transparency and portability; using plain SMTP abstractions like Nodemailer reduces dependency on any one vendor. Simple UI state and lightweight client-side code are often enough for course platforms, especially when most complexity lives in the back end and admin systems.

Data Points: Affiliate commission: 40% - Wes says affiliates receive 40% of profits from sales they refer. Backblaze download cost: 2 cents per GB - Wes compares Backblaze B2 download pricing to Amazon S3. Amazon S3 download cost: 5–12 cents per GB - Wes notes S3 can cost 5–12 cents per GB depending on region, especially for international downloads. Vimeo Pro annual price: $200/year - Wes describes Vimeo Pro as a low-cost way to stream large amounts of video. Unsupported/expensive Amazon bandwidth spend: $15,000–$20,000 - Wes estimates he may have paid this much over time in Amazon bandwidth bills. Bandwidth bill reduction: Thousands/month to under $100–$200 - Wes says moving to Backblaze and better compression reduced monthly bandwidth costs dramatically. YouTube free course promotional code: 20 free courses - Sponsor promo: syntax_free offered for the first 20 claims. Secondary sponsor discount: $10 off - After free courses are gone, code syntax gives an extra $10 off. Number of course series: 72 series - Wes mentions having about 72 series on Level Up Tutorials. Free tier usage: 15% of monthly bandwidth - Wes says his Cloudinary usage is about 15% of the free plan bandwidth at month’s end. Sales ratio tracking: Free vs paid ratio - Wes says he tracks the ratio of free courses to paid courses in his admin dashboard. Example course signups: 129 vs 54 - Wes describes bar charts comparing signups for JavaScript 30 and Redux courses. Email provider pricing: $1 per 1,000 emails - Wes describes Postmark as very affordable at scale. Mandrill free tier: 10,000 sends - Wes recalls Mandrill’s old free allowance before policy changes.

Pivotal Quotes: "“I lovingly call this thing the boss monster because it is an entire stack that powers all of my courses, all of my paid video courses, as well as all the freebies.”" — Wes Bos: Wes describes the scope and complexity of his custom course platform. "“It’s basically just a node site and has some nice little features for communicating with the front end.”" — Scott Tolinski: Scott summarizes why Meteor fits his back-end workflow and integration needs. "“I just want it to work and I want to enjoy my weekends.”" — Wes Bos: Wes explains why he prefers managed hosting and reduced server maintenance.

Implications: For developers building content businesses, the episode shows that custom infrastructure can pay off when pricing, access, analytics, and delivery need to be tightly controlled. It also highlights a practical lesson: optimize for maintainability, portability, and cost, not just novelty.