Re:The architecture of Uber’s API gateway
by alufers on Saturday May 22, 2021 @07:28PM
(#27251167)
This GUI must have a pretty advanced versioning and rollback support, otherwise I can see one user borking the whole API with a bad change and nowwhere to check what happened.
[ Parent
| on HN ]
It did not. The deployment system at Uber was a f*ing nightmare.
Things would fail, rollback, and then the logs would have their errors truncated or something. I wasted so many days deploying botched releases from coworkers.
And the use of Phabricator at Uber was a nightmare. LLVM uses it correctly, IDK what Uber did but it was a PITA to do really anything.
Pair that with the siloed off teams where "every team is its own startup" mentality and you have constant fighting, power grabs, being blocked all the time, etc.
Look at it positively. At least the rollback is working. Our version of rollback is to redeploy the old version and hope that the database migrations will work with the old one.
That was absolutely a problem at Uber, too.
Re:The architecture of Uber’s API gateway
by throwawayuber29 on Saturday May 22, 2021 @08:10PM
(#27251370)
Former Uber employee who worked on this system. It maps changes onto git changes (technically Phabricator diffs) and this system open the diff for you.
Just to add, the changes are just config changes at this point and not code changes.
One one user talking own all APIs, the system has ability to skip unmountable APIs, but we catch it during user interactions with tons of test and validations.