The Secrets to Smart, Flexible, Self Describing API
summary
Compares SOAP, REST/OpenAPI, GraphQL and gRPC with concrete trade-offs: gRPC wins for raw performance but locks clients to compiled schemas, GraphQL lets clients shape representations at the cost of scaling complexity, OpenAPI adds tooling and testing, while JSON-LD + Hydra (and schema.org vocabularies feeding Google’s Knowledge Graph) deliver the most self‑describing, evolvable APIs; Marcus Lanthaler’s generic Hydra client proves hypermedia can generate UIs and roughly half the indexed web already embeds linked data.
AI-written summary · about
chapters (10)
- 0:00Introduction and passion for APIs
- 7:51Defining flexibility and smart APIs
- 18:29API architecture decisions and trade-offs
- 26:20Evolution of API styles and SOAP
- 30:59REST principles and resource abstraction
- 39:27GraphQL, gRPC, and JSON-LD
- 44:05Linked Data and hypermedia APIs
- 51:54Hydra and self-describing APIs
- 57:10Future of data-centric architectures
- 59:59Conclusion and Q&A
related talks
51mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma
43mComparing API Protocols - One Feature at a Time
01h 01mAn Architect's Approach to API Strategies
59mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma
24mGraphQL, gRPC, REST, Oh My! - A Method for Unified API Design
30mGraphQL, gRPC and REST, Oh My! A Method for Unified API Design
18mGraphQL, gRPC and REST, Oh My! A Method for Unified API Design
48mHow to Design APIs: Swagger, gRPC, GraphQL — Which to Choose?