gofr-dev / gofr-dev/gofr

POC : Identify Gaps between gRPC and HTTP services in GoFr

Open
#2,576 2 comments 0 reactions 0 assignees View on GitHub
go Research
Dominant language
Go
Stars
20.9k
Forks
1.8k
Avg merge
5d 18h
Merged PRs (30d)
39

Description

Currently we have support for gRPC and a well extensive support for HTTP Services. We need to identify the gaps between both and close them. Since we want to enable accelerated microservice development in our microservices, our set of features for both the features must be extensive and complete for production ready systems.

Contributor guide

Open the contributing guide

Research direction

Start by comparing GoFr's existing gRPC and HTTP service support to identify concrete feature gaps. Define the production-ready parity requirements before making changes; done means the gaps are documented and the agreed missing capabilities are implemented.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, grpc
Domain
backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.