Create API for your databases, Rest, GraphQL, gRPC which one should you choose ?
summary
KillrVideo implements REST, gRPC and GraphQL in Java, C# and Node to compare real tradeoffs: REST maps naturally to synchronous CRUD and OpenAPI but returns large payloads; gRPC uses protobuf stubs, generates client/server code and excels at async streaming and low-latency RPC; GraphQL gives clients field selection and a single discoverable schema but adds server-side resolver complexity and versioning headaches. Cassandra schema forces denormalization — one query often means duplicate tables per entity — and code uses batch statements and sync vs async DAOs. All three implementations run and are on GitHub as working references.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:32Objectives
- 1:51Data model design
- 2:37Conceptual Data Model
- 3:14Logical Data Model
- 3:52Physical Data Model
- 4:13Databases access patterns
- 5:43Tools in Action
- 21:38REST
related talks
51mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma
01h 00mGraphQL, REST or RPC? Making the choice!
54mGraphQL — Usable API or Just Another Hype?
41mDoes Your API Need a REST? Check Out GraphQL.
54mTake Control Of Your APIs With GraphQL
47mMoving beyond REST: GraphQL and Java & Spring
26mRest, GraphQL & gRPC
55mGraphQL - APIs the New Way