[00:02] your system design interview, you might be in trouble. There's actually three protocols that are worth knowing, and each one has a job. REST is certainly your default choice for CRUD operations. Resources as URLs, verbs as actions, and
[00:15] it rides on top of HTTP, so you inherit caching, retries, and status codes for free. But then there's GraphQL, which is great for product UIs that need flexible, nested data. Clients can write a query describing exactly the shape of
[00:28] the data that they want, and the server returns that, no more or no less. So you like there might be with REST. Lastly, there's gRPC. It's for internal service-to-service calls where you want speed and strict contracts. Binary over
[00:43] HTTP/2, protocol schemas generate typed clients in every language, and you get streaming and multiplexing built in. It's significantly faster than JSON over REST when you're making millions of calls between services. So in your
[00:55] for GraphQL when the client needs flexible or deeply nested data, and drop in gRPC when you're designing inter-service communication at scale. either over on YouTube or on hellointerview.com.