Pragmatic Lessons of Rails & Ruby in the Enterprise
summary
An account of adopting Rails and Ruby inside Cerner gives concrete fixes and failures: Rails powers the Healthy Intent SaaS and many REST APIs, hundreds of apps and 50–100 Rails projects across the company, Rails apps run with Passenger and MySQL, services use Java, HBase and Solr, and a bad choice of Thrift forces later replacement. Ops and compliance drive tooling: Chef, a homegrown Roll Out project YAML tool for reproducible builds and auditable test artifacts, plus SAML federation and per‑action clinical auditing.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 2:45Cerners Web Development History
- 9:32Mobile Development History
- 17:17Security
- 19:53Federated Authentication
- 21:49Authorization
- 24:30Development Ecosystem
- 25:12Gem Management
- 27:12Builds
- 30:15Dependency
- 33:47Culture Shock
- 35:07Fear of Dynamic Typing
- 37:01Micro Frameworks
related talks
34mIndustrial Rails
29mLessons From A Rails Infrastructure Team
40mRunning a Government Department on Ruby for over 13 Years
35mCI/CD and devops with Ruby and Rails
33mRails is Just Ruby
46m365 Days Later: Moving from Java to RoR and how it changed everything
01h 03mRuby at Scale
34mService Oriented Architecture at Square