A Polygot Heroku
summary
Heroku moves from Bamboo to the Cedar stack, adds first-class support for Java, Node, Python, Clojure and Scala, and replaces baked-in Ruby build logic with pluggable buildpacks so language-specific installs and custom compiles run cleanly. Procfile process types, streaming logs enabled on every app, and Heroku run one‑off dynos isolate consoles. Bundler latency drops from ~18s to ~3s with API indexes, MRI 1.9.3 support lands, and a custom NES buildpack successfully boots a playable game. Resque v2 adds blocking multi‑queue and threaded vs fork consumers.
AI-written summary · about
chapters (12)
- 0:00Polyglot Heroku intro
- 1:08Cedar stack process types
- 4:46Heroku run and languages
- 5:50Build packs architecture
- 8:39Basic build pack example
- 11:30Ruby build pack compilation
- 14:18Cedar add-on changes
- 16:51Ruby language pack upgrades
- 19:44Bundler 11 performance
- 21:11Ruby 3 and multiversion
- 22:16Resque 2 improvements
- 25:52Q&A
related talks
55mHeroku PaaS Apps to Feature your Work in any Language
41mHow To Build Your Own Heroku in 2022?
27mBuilding modern applications with data on Heroku, Salesforce, and
20mRelease Engineering For A Polyglot Team
28mDelivering Heterogeneous Architectures
27mCloud Foundry Compared with Other PaaSes
03h 04mHow We Evolve Clever Cloud – Postmortem on a 10‑Year Project
33mBuilding Shopify's PaaS on Kubernetes