John Deere Operations Center Development Journey & Ecosystems
summary
John Deere Operations Center moves from a three-part deployment to a two-part and toward a single pipeline, cutting deployment cycles by decoupling UI (hosted on S3+CloudFront) from server code, increasing automated tests and clearer contracts. Architecture uses ECS/Fargate & EB/EC2 for compute, Lambda for small support tools, ALB + OIDC and JWTs for auth, ElasticCache for state, and CDN for static delivery. Result: lower cost and faster releases, while precision tech (StarFire receivers) still deliver ~2.5 cm positioning.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:54Intelligent solutions group
- 2:38Operation center
- 3:47Overview of application architecture
- 8:37Journey from tripods to monopod
- 9:08Let's build web apps
- 9:32Auth layer
- 14:23Compute layer
- 18:35Outro
related talks
32mLearnings from a DevOps Organization in the Making
29mTaming the Hybrid Beast with DevOps
40mEnd User Town Hall
47mDevOps in a multicloud environment with CloudCenter
42mOperability and You Build It You Run It
25mChanging the Development Culture at Comcast and Our Evolution from Legacy SOA to Cloud Native
30mThe Journey from Print to Online Journalism is Cloudy
42mAutomation, Innovation and Continuous Delivery
