3 ms·

One of the authors here, happy to answer questions.

• bilal4hmed 5y ago
  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?
  • madan 5y ago
    Since the final artifact was generated, we were able to work around by annotating in thrift with alternate field names.
    • exhaze 5y ago
      Just make sure to not accidentally add an extra space in the Thrift annotation, or else it will globally bring down upfront pricing
• DandyDev 5y ago
  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?