Low interval update resources and server requirements

Quoting the official fivem site:

What are the system requirements to run a server?

We recommend a x86-64 system running Linux or Windows (7/2008 R2+), decent upstream connectivity and preferably a multi-core processor.

The server requirements seem really low, this looks too good to be true at best and suspicious or dishonest at worst. What is the catch?

I’ve noticed that many of the popular resources (like esx_framework for example) have most of the important logic client side - taking the load off the server, but making it really vulnerable to tampering, hacking or bypassing.

I’d like to know if it’s actually possible to write resources that require updates on intervals of less than one second in a safer way (much less client side and much more server side) and still use a decent amount of them without these requirements skyrocketing or just straight up butchering performance.

If it’s actually possible, how would one go about it? I’m guessing that there is no Citizen.CreateThread call server side (at least I’ve not seen it in a server script like ever) and therefore it could not be as simple as moving all the work-intensive threads to server scripts.

‘anything that’s not trash’ is not really ‘low’

yeah, why not?

there is.

why guess when you can read:

https://runtime.fivem.net/doc/natives/ with ‘server’ ticked + https://docs.fivem.net/docs/scripting-reference/runtimes/lua/server-functions/

definitely is, again, except the amount of available getters/setters is limited as these are a community effort