How Toyota Motor Europe use Heroku
summary
Toyota Motor Europe migrates customer-facing sites from manual .NET/XML servers to a Node-based, PaaS-driven model on Heroku, replacing slow two-day deploys with automated pipelines, Bamboo + Stash for CI and New Relic for visibility. Production is cloned per market so each country runs isolated stacks and can scale by turning up dynos—benchmarks lead to two dynos for Germany as a sizing rule. A custom buildpack (Google pagefeed) is built and deployed; outages are rare and platform API issues occur twice in months.
AI-written summary · about
chapters (5)
- 0:00Start
- 4:31Supply Chains
- 11:45Where Do We Build Our Factory on the Cloud
- 13:27Why Did We Go with Heroku
- 15:26Platform Api
related talks
55mHeroku PaaS Apps to Feature your Work in any Language
01h 29mTutorial: Build Your Own Heroku With Cloud Native Stack
48mOne and a half year with Heroku-like PaaS
24mContinuous Deployment at Scale
34mKubernetes from Dev to Prod at GoEuro
31mHow a Top European Cloud Provider Migrated to Terraform Enterprise
35mRoad to Efficient and Data-Driven DevOps
31mLiving in a Hybrid World