Designing API: REST, gRPC or GraphQL?
summary
Demo builds the same Java API three ways on Apache Cassandra using a table-per-query model (two comment tables for user and video) and a small Maven project; test data yields paging and works in browser after a restart. REST gives HTTP verbs, Swagger docs and fits API‑management tooling; gRPC uses a proto file, generates client/server stubs, uses protobuf binary serialization and favors streaming and low latency but limits nested depth; GraphQL exposes a single endpoint with GraphiQL discoverability and smaller payloads; schema edited in DataStax Studio.
AI-written summary · about
chapters (6)
- 0:00Start
- 4:42Data is distributed
- 5:09Data is replicated
- 5:44Tuneable Consistency
- 8:08Api Design Methodology
- 8:36Designing Data Model
related talks
55mBuild APIS with SpringBoot - REST, GRPC, GRAPHQL which one should you pick? Cedrick Lunven
46mREST API vs gRPC, which one should you use in breaking a monolith
41mDoes Your API Need a REST? Check Out GraphQL.
59mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma
43mBeyond REST API’s – An overview about modern API technologies
01h 15mREST, GraphQL, and gRPC: A Comparison
43mTUTORIAL: We've "REST"ed long enough -- let's have an API adventure!
28mBetter APIs through Better More Timely Data