News for hackers. Stuff that matters.
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.
Re:The architecture of Uber’s API gateway by DandyDev on Sunday May 23, 2021 @06:38AM (#27253986)
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?

Re:The architecture of Uber’s API gateway by madan on Saturday May 22, 2021 @11:29PM (#27252183)
Since the final artifact was generated, we were able to work around by annotating in thrift with alternate field names.
Re:The architecture of Uber’s API gateway by exhaze on Sunday May 23, 2021 @01:17AM (#27252625)
Just make sure to not accidentally add an extra space in the Thrift annotation, or else it will globally bring down upfront pricing