Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add gRPC Support for Enhanced Communication Efficiency #2663

Open
hbenali opened this issue Dec 10, 2024 · 0 comments
Open

Add gRPC Support for Enhanced Communication Efficiency #2663

hbenali opened this issue Dec 10, 2024 · 0 comments

Comments

@hbenali
Copy link
Member

hbenali commented Dec 10, 2024

Is your feature request related to a problem? Please describe.
Currently, Meeds relies on existing APIs for client-server communication. While functional, these APIs may encounter performance, scalability, and interoperability limitations when handling high-frequency, low-latency requirements.

Describe the solution you'd like
Implement gRPC (gRPC Remote Procedure Calls) as an alternative communication protocol to REST APIs. gRPC supports efficient, binary serialization using Protocol Buffers, enabling faster data transfer, bidirectional streaming, and support for multiple languages. This addition would improve overall communication performance and make the system more flexible for developers.
Describe alternatives you've considered

  • Using WebSockets for real-time communication doesn't offer the same efficiency or native support for multiple languages that gRPC provides.
  • Optimizing REST API endpoints, which could help but doesn't fully address the need for streaming or binary serialization.

Additional context
Adding gRPC support would benefit developers building performance-intensive integrations, especially applications requiring real-time data streaming (like activity streams) or interoperability with other gRPC-based services.

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant