Re:The architecture of Uber’s API gateway
by madan on Saturday May 22, 2021 @10:20PM
(#27251932)
One of the authors here, happy to answer questions.
[ Parent
| on HN ]
Did you consider using existing API Gateway solutions, either OSS or commercial? Why did you decide to build your own?
Given that Uber is an engineering heavy and tech-centric organization, why did you choose to do configuration through the UI? Why not configuration and infrastructure as code?
Re:The architecture of Uber’s API gateway
by bilal4hmed on Saturday May 22, 2021 @11:08PM
(#27252108)
The issues that you had with Go 'Language naming conventions like ID, HTTP, and reserved keywords in Go (but not in Thrift) created failures that exposed the internal implementation details to the end users.'
How did you go about solving those ?
Did yall work with the Go team to resolve the other issues that were stumbled upon?
Since the final artifact was generated, we were able to work around by annotating in thrift with alternate field names.