Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

50%
+0 −0
Q&A Best practices for designing a central gateway/hub for microservices communication

GraphQL instead of gRPC Assuming you do decide to implement a gateway, I'd consider implementing it as a GraphQL API instead of plain gRPC. I feel like your usecase is almost exactly what it's int...

posted 22d ago by Iizuki‭

Answer
#1: Initial revision by user avatar Iizuki‭ · 2025-03-11T08:59:02Z (22 days ago)
# GraphQL instead of gRPC

Assuming you do decide to implement a gateway, I'd consider implementing it as a [GraphQL](https://graphql.org/) API instead of plain gRPC. I feel like your usecase is almost exactly what it's intended for. It too suports streaming, plus it's just a pleasure to work with in general. Easy to document, evolve etc.