prodbro

I'm still working on my Web Server Library .NET Core, the rewrite is almost finished (beta version)

https://simplew.net/

I'm still working on my Web Server Library .NET Core

I'm rewriting from scratch : https://simplew.net/v26/

I'm still working on my Web Server Library .NET Core https://stratdev3.github.io/SimpleW/

I'm rewriting from scratch : https://github.com/stratdev3/SimpleW/releases/tag/REWRITE

I'm working on my side project on my free time, a web server library .NET Core https://stratdev3.github.io/SimpleW/

VitePress saved my day.

The default template is great and everything in VitePress has been thinking to create documentation. Very nice project.

There's also Fast Endpoints[1]

thank for the pointer !

The syntax seems cool and comprehensive, i like it.

I made some test and like its name, it is very fast : performances are closed to SimpleW, just a little bellow. But its memory footprint is the half, so i'm impressed. I will check the code, sure there are interesting things into.

There are probably some optimizations to improve the Kestrel

You're right.

To be fair, i have to run many other benchmarks including one with the best recommanded optimizations for each projects.

a little time consuming but definetely on my todo list.

those opinions most sense for VAST majority of their users

I have a much more nuanced view.

I think that ASP.Net is the de facto standard for being backed by Microsoft since many years. From the gold time when ASP means IIS to now when Kestrel was cannibalized by Microsoft.

As a developer, working with the most widely used stack guarantees that these choices won’t be questioned in critical situations. I’m not saying Kestrel is bad, but it doesn’t automatically fit every scenario.

- 15 years ago, there were Apache or IIS.

- Then nginx changes the game and kicks their ass

- Then webserver starts being written into script langage for better integration (Ruby, Python), no more CGI and nginx as reverse

- Then node changes the game

- Now : caddy and other alternatives... but still not web server in PHP (troll inside)

I see a pattern to not believe aspnetcore is the only one and the best.

I hate when someone's software advertises itself as 'blazingly fast' and then provides NO DATA to back up the claim

agree, that's why there is a performance benchmark at https://stratdev3.github.io/SimpleW/guide/performances.html with code as you can reproduce at your own.

i'm adding other tests, more complete than the hello world one.

Does this mean a developer doesn't have to install nginx or iis ?

author here.

You don't have to keep it behind a reverse proxy like nginx.

But you can, especially if you have multiple APIs and you want to keep thing separated for security reason.

Example :

nginx:443 (reverse proxy, domain name routing)

|

|-> website1:8081 - docker container with SimpleW

|-> website2:8082 - docker container with SimpleW

|

...

ASP.NET Core is one of the best web frameworks

I don't think so.

The fact is there are very few dotnet web servers. ASP.NET Core is supported by the owner of the dotnet langage who is also the M of the GAFAM.

There is some place in the ecosystem for other alternatives

The library's tagline says "Powerfully Simple. Blazingly Fast."

Joking aside

author here.

I agree with your remark ^^

Each time i read some news about a new framework with tag "blazingly fast", i'm thinking "lol".

So i had to resist to the temptation... And finaly when doing a small benchmark, performances were not bad at all (https://stratdev3.github.io/SimpleW/guide/performances.html) and i let the "clickbait" title.

My targets are small to medium traffic and embeded devices (dotnet/android).

author here.

that's the reason why i start the project. I had time and wanted something simple as my needs.

author here.

I wanted to start with something small where I could read or write the code in a reasonable amount of time.

My usage was, and still is, for low traffic. I don't intend to replace the Kestrel beast.

Just a framework you can quickly understand without being lost in documentation once you want to custom a part.