Live data from Hacker News

Microsoft YARP

github.com

101–110 of 153 posts

Re: Microsoft YARP

#101
post #30

How does this compare to nginx? Does it support websockets? I have an asp.net core websocket based app that need to support hundred of thousands concurrent websockets connection. I ll be taking a look at this because I don't wanna expose Kestrel directly to the internet.

The main difference I see is that YARP is added right into the dotnet project itself. See the getting started : https://microsoft.github.io/reverse-proxy/articles/getting-s... From my understanding Kestrel passes request to this. > The proxy server is implemented a plugin component for ASP.NET Core applications. ASP.NET Core servers like Kestrel provide the front end for the proxy by listening for http requests and t…

So, basically vendor lock-in is the difference?

Re: Microsoft YARP

#102
post #86
post #44

Earlier quoted context omitted.

There aren't a lot of good proxy development frameworks. There are decent lower level libraries, and proxy servers with limited scriptability. I've spent the last 4 years at Fly.io wishing for a nice, full featured, proxy framework. This looks pretty darn good to me.

A Ruby on rails shop like fly.io would use .net?

I think we have more Rust and Go than Ruby at this point. Probably slightly less Elixir.

For better or worse we're not really fixated on one language.

Re: Microsoft YARP

#103

YARP is yet a another example of how C# is becoming a dominant systems language. The ease with which you can build a tailor-made reverse proxy is pretty amazing.

>C# is becoming a dominant systems language

In 2022 everything is a system programming language. Next on that list is Javascript, I am sure.

Re: Microsoft YARP

#104
I am late to the party here.

What is the purpose of a reverse proxy?

Reading online: security, load balancing, https seems to be mentioned.

It appears a bit to me that a reverse proxy is not doing what a web server used to do back in the days of IIS/Apache.

I see a lot of programs meant to operate on the web that use very simple http servers.

Re: Microsoft YARP

#105

>> 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?

Microsoft employees here. No actually. It's probably via word of mouth that they realized people are reinventing the wheel.

Re: Microsoft YARP

#106

Sometimes it feels like Microsoft and/or C#-enjoyers just want to re-implement everything that already exists. While having many implementations to choose from if you need to select a solution to an outstanding problem is great, it makes me wonder why re-implementing something with no discernible benefit keeps eating time/resources all over the place. In similar cases of implementing reverse proxies in C, C++, Rust,…

>Sometimes it feels like Microsoft and/or C#-enjoyers just want to re-implement everything that already exists It sometimes feels to me, like a huge percentage of developers reinvent the wheel

Ah, that is why cars still use chariot wheels.

Re: Microsoft YARP

#107
post #32

Earlier quoted context omitted.

Would your reaction have been different if, instead of Microsoft, this article was submitted by some random person entitled "Show HN: I built a reverse proxy in C#"? By your logic, the world should be operating on a single OS, with a single web browser, paired with a single web server, because why re-implement something that already exists?

Pretty much every "I built a thing" post is met with the same response. MS isnt special. I think pretty much every open source project that wants to be taken seriously needs to compare itself with its competitors.

Nope, if it is an HN hyped language it gets all the love of the day, Ruby, Clojure, Rust,....

Re: Microsoft YARP

#108
post #98

Earlier quoted context omitted.

It's only in the last 5 years that .NET was open sourced and made available officially for Linux systems. Up until then most C# use was strictly on Windows, and OSS especially for Windows server side stuff (IIS, SQL server, etc.) was (and still is) pretty rare. I've seen windows server places (Microsoft) implement everything from redis, memcached, queue systems, prometheus, lucene, DNS servers, to reverse proxies, et…

C#/.NET/CLR are competing against Java/JRE/JVM. So reinventing "everything" in a Windows Server environment is slowly coming to an end, with Windows server becoming a hypervisor for VMs/containers and a runtime for .NET/CLR. The economics of getting all of the FOSS infrastructure tooling in a "Windows native" form is being beaten by just running them in containers/VMs on whatever hypervisor is available. In the same…

Linux is being replaced by type 1 hypervisors, no need for Linux to run a container runtime.

Re: Microsoft YARP

#109

>> 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?

Microsoft employees here. No actually. It's probably via word of mouth that they realized people are reinventing the wheel.

You know how barnacles attach to a whale, to clean it? Maybe you guys need to spin off a whale-cleaner startup =D [edit] I realized it's the fish that clean the barnacles off it. So maybe like that. Anyway I'm just saying that an organization that is carrying that much dead weight just on internal organization is probably desperate for some better method than word of mouth to identify stuff like that.

Re: Microsoft YARP

#110

>> 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?

I did worked with MSFT for some time. Basically you can do your own stuff, until you need to go to production. And if you do all things right "per process" somebody will "glimps" into your architecture and maybe even code. And in most cases this particular individual has seen a lot and is in the position to identify patterns. TBH I quite enjoyed how their corp machinery is working in the cloud world.
Post reply on HN