REST, gRPC, GraphQL or Asynchronous Messaging
Be it any industry, applications need to talk to each other. So, developers often build bridges – Application Programming Interfaces (API) – to allow one system to communicate with another. REST, gRPC, GraphQL and Asynchronous Messaging are all patterns of communication between distributed systems. What are the core concepts behind these patterns? Do you know what problems they try to address? What about the use cases? Join my session to find out the answers to these questions!
A big shout out to my colleagues Szymon Pobiega and Tomek Masternak for helping me validate all the content for my talk. Thank you, Szymon and Tomek!
Resources
- Article Series
- RESTFul API
- Web API Apps
- REST API Design Best Practices
- Richardson Maturity Model
- GraphQL
- Hot Chocolate Docs
- gRPC
- gRPC MS Docs
- Comparing SOAP vs gRPC vs REST vs GRAPHQL APIs
- REST vs GRAPHQL - A Critical Review
- My comparison of APIs
- My blog on Async Messaging
- Messaging Concepts
- Free Online Course - Distributed Systems Design Fundamentals
- Advanced Distributed Systems Design
- Distributed Computing Fallacies
- RPC v/s Messaging. Which is faster?
- Getting Started with NServiceBus