How to tackle the reusability problem in the software industry
summary
Argues reusability works only inside domains and succeeds when components have the right size, are interoperable and discoverable; cites a four-rule checklist and warns about team dependencies. Shows practical stack: serverless functions (AWS Lambda/Azure/GCP), decoupled frontends, microservices and GraphQL as a typed query language that federates many back ends. Calls out real failures: resolver performance bottlenecks, federated mutation complexity and release coupling. Announces code.store and an upcoming GraphQL native API gateway as a marketplace/NPM-for-APIs experiment.
AI-written summary · about
chapters (7)
- 0:00Intro
- 1:32What is reusability
- 2:52How to enable reusability
- 5:03Why you should care
- 10:23GraphQL and domain design
- 16:22Future of Apis
- 17:25Questions
related talks
43mGraphQL in the Era of Server Components
57mForking the Future: Embracing Microservices Evolution
30mGraphQL in the Era of React Server Components
30mReact state management in a GraphQL era
31mReimagining the frontend-backend divide thanks to GraphQL
27mWhat if ... How to Achieve GraphQL Domination
29mWrite Queries, Not Code
15mThe Right Size For GraphQL