Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft YARP

github.com

Post reply on HN
Print view View original

91–100 of 153 posts

Re: Microsoft YARP

#91

Post by square_usual »

throwuxiytayq wrote: post #87
mukundesh wrote: post #85

Only available in .NET ecosystem, got excited after I read the title, but forgot Microsoft is Microsoft. "YARP is a reverse proxy toolkit for building fast proxy servers in .NET using the infrastructure from ASP.NET and .NET."

I don't get it, what do you even expect them to do ? Write it in Java? It's MIT-licensed, you can rewrite it if you wish.

Yeah - whatever language they chose it would be "only available for [that] ecosystem." At some point you've got to pick your home, not like you can write a 100% cross-language framework for anything.

Re: Microsoft YARP

#92

Post by pdpi »

mukundesh wrote: post #85

Only available in .NET ecosystem, got excited after I read the title, but forgot Microsoft is Microsoft. "YARP is a reverse proxy toolkit for building fast proxy servers in .NET using the infrastructure from ASP.NET and .NET."

It’s written in C#, probably because they use a bunch of C# internally for this sort of project (who’da thunk it?). That naturally restricts the project to .NET environments.

That line could easily have read “for building fast proxy servers in the JVM” or “for building fast proxy servers in node.js” or whatever else, and it would’ve still been just as restrictive.

Re: Microsoft YARP

#93

Post by oaiey »

rafale wrote: post #40
politelemon wrote: post #36

Earlier quoted context omitted.

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…

I see. So it can operate in-process? Could in theory be much faster than nginx out-of-process model.

I think it either operates as a traditional (heavily customizable) reverse proxy OR you have a app and forwards x% of your API surface to second tier services.

Imho: no in-procees reverse proxying. That should not make sense.

Re: Microsoft YARP

#94

Post by oaiey »

js4ever wrote: post #86
mrkurt wrote: 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?

He explains the use case why you need a RP framework in your language of choice not his desire at fly.io (I guess :))

Re: Microsoft YARP

#95

Post by oaiey »

qbasic_forever wrote: post #19
oneplane wrote: post #14

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,…

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…

And that is not a gut prediction but history. 15 years ago the default was Windows, .NET and SQL Server. 5 years ago it is Linux in the cloud, .NET and PostgreSQL.

Re: Microsoft YARP

#98

Post by rswail »

qbasic_forever wrote: post #19
oneplane wrote: post #14

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,…

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 way, Linux is becoming a hypervisor for containers and the various container runtimes.

Re: Microsoft YARP

#99

Post by older »

jeeeb wrote: post #29
bob1029 wrote: post #18

Earlier quoted context omitted.

> re-implementing something with no discernible benefit keeps eating time/resources all over the place. > is a shame considering the benefits of pooling resources on existing implementations would have. What exactly would you prefer these developers spend their time on instead of this work? There are a lot of benefits to being able to integrate your own reverse proxy directly into your software stack. C# developers e…

> There are a lot of benefits to being able to integrate your own reverse proxy directly into your software stack. C# developers enjoy these as much as anyone else would. I take this at face value but it would be nice to know what the benefits are vs nginx and other off the shelf solutions. The readme explains the benefit for Microsoft but not how it stacks against off the self solutions.

One benefit is that you can run it on your existing IIS cluster where you already run yor stuff.

Re: Microsoft YARP

#100

Post by noduerme »

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

Post reply on HN