Feature: gRPC #341

New issue

Open

opened 2025-06-28 23:09:09 +00:00 by jamie · 0 comments

jamie commented

2025-06-28 23:09:09 +00:00

(Migrated from git.hazaar.io)

Problem Statement

Hazaar currently relies on traditional HTTP-based communication for server-to-server and microservice interactions. Modern microservice architectures often use more efficient communication protocols such as gRPC to achieve better performance, type safety, and interoperability between services. Investigating whether gRPC would be a valuable addition to Hazaar is necessary to ensure the framework stays competitive and scalable.

Who will benefit?

Developers building microservice architectures on Hazaar.
Teams requiring high-performance server-to-server communication.
Applications that benefit from strongly typed APIs with low-latency transport.

Benefits and risks

Benefits:

Potentially improved performance and reduced latency for inter-service calls.
Language-agnostic and strongly-typed APIs via protocol buffers.
Easier cross-language service integration.
Supports features like streaming and bi-directional communication.

Risks:

Adds complexity to the framework and learning curve for developers unfamiliar with gRPC.
Requires careful evaluation of PHP gRPC client/server support and its maturity.
Increased dependencies and possible compatibility issues.

Proposed solution

Create a research and feasibility task to investigate:
- PHP support for gRPC servers and clients
- Compatibility with Hazaar’s architecture
- Performance gains over traditional HTTP APIs
- Integration requirements with existing Hazaar routing and models
Produce a recommendation report based on findings.
If deemed beneficial, develop a module or integration for Hazaar that provides:
- gRPC server handler
- Client libraries
- Developer tooling and documentation

Examples

Symfony has gRPC bridges available for inter-service communication.
Go and Java frameworks often use gRPC for microservices to improve performance and reliability.

Priority/Severity

High (This will bring a huge increase in performance/productivity/usability/legislative cover)
Medium (This will bring a good increase in performance/productivity/usability)
Low (anything else e.g., trivial, minor improvements)

## Problem Statement Hazaar currently relies on traditional HTTP-based communication for server-to-server and microservice interactions. Modern microservice architectures often use more efficient communication protocols such as gRPC to achieve better performance, type safety, and interoperability between services. Investigating whether gRPC would be a valuable addition to Hazaar is necessary to ensure the framework stays competitive and scalable. ## Who will benefit? - Developers building microservice architectures on Hazaar. - Teams requiring high-performance server-to-server communication. - Applications that benefit from strongly typed APIs with low-latency transport. ## Benefits and risks ### Benefits: - Potentially improved performance and reduced latency for inter-service calls. - Language-agnostic and strongly-typed APIs via protocol buffers. - Easier cross-language service integration. - Supports features like streaming and bi-directional communication. ### Risks: - Adds complexity to the framework and learning curve for developers unfamiliar with gRPC. - Requires careful evaluation of PHP gRPC client/server support and its maturity. - Increased dependencies and possible compatibility issues. ## Proposed solution - Create a research and feasibility task to investigate: - PHP support for gRPC servers and clients - Compatibility with Hazaar’s architecture - Performance gains over traditional HTTP APIs - Integration requirements with existing Hazaar routing and models - Produce a recommendation report based on findings. - If deemed beneficial, develop a module or integration for Hazaar that provides: - gRPC server handler - Client libraries - Developer tooling and documentation ## Examples - Symfony has gRPC bridges available for inter-service communication. - Go and Java frameworks often use gRPC for microservices to improve performance and reliability. ## Priority/Severity - [x] High (This will bring a huge increase in performance/productivity/usability/legislative cover) - [ ] Medium (This will bring a good increase in performance/productivity/usability) - [ ] Low (anything else e.g., trivial, minor improvements)