Is it good enough for a dynamic web server nowadays?

Is it good enough for a dynamic web server nowadays?

Attached: 295BDE72-1F24-4BFD-A160-4D8A9B1AEB62.jpg (1400x560, 243.99K)

It's fine
there are obviously better options but Mojo is very capable

I've heard that Mojolicious is fine. Personally Perl is fine for one liners to replace AWK and sed, haven't tried to use it for anything else

Let’s say I have a small forum with at most 200 requests per minute, would it suffice?

It's not ideal, but if you really want to, sure.

You can but why would you when i can literally name 10 better languages for a webserver.

What’s a more performant option? I hate using php and nothing else has its speed or low memory usage

>Let’s say I have a small forum with at most 200 requests per minute, would it suffice?
Anything would suffice but the question is on what infrastructure? If you use Go you could host your blog that maxes at 200 post per min on a 20$ vps.

I got a gigabyte of ram and single core vCPU

Depends. You can use Python or JS. If you want to speed things up and get an even better performance without wasting time writing boilerplate you could use C#. If you're okay with writing a lot of boilerplate code but want to be the fastest and have a low memory usage use Go.

what’s a popular go framework or library

Okay. Then Go is what you will use. It's has a very low memory footprint and is the best at concurrency in single core scenarios + it's made for i/o. If you want to make it even better use http/3. It uses UDP instead of TCP to communicate.

If you only need 200 requests per minute, pretty much any sane option would work, as long as your code is not retarded.

Gin and Beego. If you want the best possible performance you have GoFiber but you'll have to use Nginx because GoFiber doesn't have built in support for http/2 (which doesn't matter if you use Nginx).

He needs to handle 200 request per min + everything else the app will do on 1GB of RAM and 1vCPU

Yea I’ll use gofiber then since I’m already using nginx

Perl or Python would still be usable imo. 1GB is plenty for a small website.

His server will render the UI at each connexion and handle backend stuff.

Your browser "renders the UI", retard. The backend part is only hard if you have complex needs (i.e. not a forum) or need it to be very fast.

GoFiber is so fast because it's built upon fasthttp user. Concurrency is easy to do in Go so you should even handle thousands of concurrent requests on your 1gb 1vcpu server. If you really want a better performance the real bottleneck (as it has always been) is the database.

I meant will serve the UI not render.

For the database -unless you expect that your database will someday have more than 100k hits/day- the best performing and less memory consuming one is SQLite.