Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In the video titled 'RPC Frameworks Overview' presented by Yulia Oletskaya at the Balkan Ruby 2019 conference, the main focus is on Remote Procedure Calls (RPC) and their increasing relevance in web development, especially in the context of microservices architectures. Yulia begins with a definition of RPC, emphasizing its role as a protocol for one program to request a service from another located on different computers. She explains that despite being conceptualized in the 1970s, RPC has gained momentum in the modern web development landscape. Key points discussed include: - **Migration Experience**: Yulia shares her experience with migrating a system from an internal RESTful JSON API to an RPC-based architecture involving over 50 services. - **Technical Stack**: The new architecture includes an RPC server and utilizes Amazon SQS for messaging, improving performance through direct service communication and maintaining schema consistency for easier versioning. - **RPC Frameworks Overview**: The talk highlights various RPC frameworks such as gRPC, Apache Thrift, and Cap'n Proto, detailing their advantages and disadvantages: - **gRPC**: Popular due to its support from Google, it offers efficient serialization with protocol buffers but has caveats such as a delay in language updates. - **Envoy**: Designed to support gRPC and tackle load balancer issues, this framework enhances ease of use but is limited in some advanced features. - **Apache Thrift**: An older framework with extensive language support, yet with lesser community engagement compared to gRPC. - **Cap'n Proto**: Claims higher speed than gRPC by not relying on traditional encoding but has limited Ruby support. - **Conclusion**: The importance of selecting the appropriate RPC framework based on application needs is underscored. Yulia concludes the talk by encouraging the audience to consider their specific requirements when choosing an RPC solution. Overall, this presentation provides valuable insights into the various RPC frameworks available and practical migration experiences from traditional APIs to more modern, efficient communication protocols.
Suggest modifications
Cancel