Programming

17408 readers

75 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

[email protected]

Building out a central management console for various services in org. What's the right architectural approach? (programming.dev)

submitted 1 year ago by [email protected] to c/[email protected]

2 comments fedilink hide all child comments

In a software org at a large tech company that has several services across small teams with various functionality and UIs. Have gotten direction from up above and been assigned the task of being responsible for concentrating all of the different services under a single web service and UI. Think AWS management console for the various AWS tools.

These services are all webservices with different communication protocols (REST, gRPC, etc) and different tech stacks internally, since they were all bootstrapped without a technical playbook in mind. What are some architectural or organizational patterns that I should look into in order to make this happen?

top 2 comments

sorted by: hot top controversial new old

[–] [email protected] 1 points 1 year ago

Graphql federation could help unify these services behind a single API.

[–] [email protected] 1 points 1 year ago

I would look at the patterns used by successful open source projects in this space, or actually use those projects directly.

https://github.com/Kong/kong works in this space, but there's like a million of them. I'm not super familiar with the space, but I'd look through a list like this: https://dev.to/apisix/how-to-choose-the-right-api-gateway-3f9i

And decide if you're open to a commercial solution, want to directly eval open source options, or if you think you're genuinely resourced to create something bespoke that's better and just want want to study the OSS options for inspiration. Nothing in this question makes me think you'll arrive at a better result through custom code than you would through adopting a mature API gateway, but who knows.