Moving from Anarchy to Sustainability
summary
Company moves from 130 different apps and a chaotic API landscape (400+ public endpoints, ~650 internal) into a single-page one application built from reusable applets and declarative workflows. Front end standardizes on GraphQL + React + Node.js, back end uses a composable schema server, OAuth/OpenID Connect, Docker/Kubernetes, GitHub Enterprise + Drone and JFrog; logging with ELK and metrics via Prometheus. Architecture prototypes land in weeks, evolves over months, and becomes reasonably stable in production.
AI-written summary · about
chapters (34)
- 0:00Introduction
- 1:10What is Addform
- 2:02What is Anarchy
- 2:35What is Sustainability
- 3:16Usability
- 3:45Inconsistent User Experience
- 6:10User Facing Applications
- 6:59Navigation Map
- 7:53Goals
- 9:24The Solution
- 10:43Personas
- 11:22Standard Technologies
- 13:00Business Developer
- 14:10Frontend Components
- 14:34React Components
- 15:25Example
- 15:54A promise
- 16:22A workflow
- 16:47Finite State Machines
- 17:50Backend
- 18:22GraphQL
- 19:11Schema
- 19:58DevOps
- 20:26Containers
- 21:01Kubernetes
- 21:21Common Services
- 21:56Uncle Petes Advice
- 23:21DevOps Engineers
- 23:50Fashion Industry
- 24:19Adapt Retrain
- 25:08Questions
- 25:56Why Rest
- 28:12Security
- 34:28Software Engineering
related talks
28mA Real-World GraphQL Application in Production
37mGraphQL and Microservices or How we learned to be big and small at the same time
49mApplications architecture spanning multiple clouds
15mSpace, the final frontier
47mDeploying atomic design system at scale
55mFront-End Independence with GraphQL and Redux
30mReact state management in a GraphQL era
46mMoving to GraphQL