connected-car.js • Lightning talk

on YouTube ↗04m

" summary

Thirty-plus staff are building connected-car services and run nine REST APIs that used to have hand-edited docs and flaky integrations. The team converts API descriptions into swagger specs, bundles response fixtures, and generates docs, runtime routes and a homemade npm module that spins up a static mock server. API changes land only in the spec, protocol tests run against the fixtures in CI, docs stay correct, and consumer breaks surface immediately so deployments stop breaking dependent services.

AI-written summary · about

" chapters (4)

1. 0:00Start
2. 0:20What Springworks are doing
3. 1:43Possible Paths
4. 1:57Generate docs & code based on API spec

" related talks

• 01h 21mContract Driven Development-Deploy MicroServices Independently W/out Integration TestingHari Krishnan, Joel Rosario · Agile India 2022
• 37mAutomation++ - Building an Enterprise API Economy from scratchRyan Coates · Automation + DevOps Summit 2021
• 22mThe dirty secrets of building large HTTP APIsDamian Schenkelmann · RuhrJS 2016
• 21mThe Dirty Secrets of Building Large, Highly Available, Scalable HTTP APIsDamian Schenkelman · NodeConf Argentina 2016
• 02h 19mLightning TalksRailsConf 2013
• 40mA Developer’s Tour in 360 DaysHervé Fontbonne, Guillaume Lieure, Jean-Charles Verazzi · DevOps D-DAY 2019
• 04mLightning Talk from Jason MalstromJason Malstrom · DevOpsDays Boston 2019
• 26mMaking internets great again - a story of working with legacy codeMiszo Radomski · ConfrontJS 2018