Live data from Hacker News

Microsoft YARP

github.com

151–153 of 153 posts

Re: Microsoft YARP

#151
post #41
post #24

Earlier quoted context omitted.

To clarify, are you saying that: 1. There are already good reverse proxy libraries in C#? 2. There are already good reverse proxy libraries in other languages? 3. There are already good reverse proxy applications ? If it's #1, then yeah, it would be nice if the ReadMe explained why YARP is different. To be fair, they're at least consolidating a bunch of efforts within Microsoft: > We found a bunch of internal teams a…

> But over time we needed to customize things in ways that were difficult to do within Nginx's architecture (either in Lua or in C), Yup. Eventually a configuration language becomes a shitty programming language, so why don't we just use a programming language?

It's the configuration complexity clock!

http://mikehadlow.blogspot.com/2012/05/configuration-complex...

Re: Microsoft YARP

#152

>> We found a bunch of internal teams at Microsoft who were either building a reverse proxy for their service or had been asking about APIs and tech for building one I'm really curious, does Microsoft have a crew of anthropologists walking around to figure out which team is reinventing wheels?

Honestly I think any company that exceeds a certain size could do with a full time team to investigate and solve NIH and duplication. I mean Google reinvents chat every couple of years, and that's just the ones that come out in public <_<

Fundamentally I believe it’s a communication problem + a problem of “engineers gonna engineer” to launch the next Big Win™ for their team / resume.

If I were looking for an honest solution for the first part, I might start with a standardized way of classifying technical problems and solitons. Maybe then it would be possible to build a directory of sorts for existing solutions that could be referenced when the need for a solution arises anywhere within the company.

Re: Microsoft YARP

#153
post #54

Earlier quoted context omitted.

Can you share more specifics on what you needed to customize that went beyond nginx's capabilities?

This was 5+ years ago so I'm a little hazy on the details. A lot of it was just plugging into our infrastructure for config, service discovery, rate limiting, logging, etc. - Logging the exact metrics we wanted to our metrics service. (We wrote a bunch of Lua code to do this.) - Loading the set of backend services from Zookeeper. (We had a sidecar process that would periodically sync from Zookeeper to a config file,…

Your application does indeed sound like it's beyond OTS solutions, thanks for sharing!
Post reply on HN