About PHP with 64-bit integer

[wonderfulShrineMaidenOfParadise]

News has dropped 32-bit PHP, so to keep using News, one has to change the hardware to 64-bit one.
But my 32-bit hardware is still something usable and I feel like to keep using it until its EOL. Not every app requires 64-bit PHP.
So I have 3 ideas:

1. A dedicated NGINX config, that handles News request with 64-bit only cluster. The rest can use a 32-bit/64-bit mixed cluster
2. Another domain for News requests
3. Another Nextcloud instance

However I have no idea how to implement 1st. Any help will be appreciated.

[SMillerDev]

None of these will help if the underlying hardware does not support 64 bit integers.

[wonderfulShrineMaidenOfParadise]

My main node is 64-bit and it has been running News since 16.0.0, so I assume that it supports 64 bit integers.
By the way does the database have to be 64 bit as well?

[Grotax]

I assume that database servers can handle also 64bit integers on 32bit systems but I'm not sure.

The PHP issue is that it never supported big numbers on 32 bit. That's just something not supported in the architecture.

News since the first day struggled with this because the api was designed to use timestamps with high resolution I think micro seconds.
To prevent some timing errors.

In the past that was then internally handled as a string, as a workaround.
But the recent needed refactoring of the code broke this workaround.

The ideal solution in my view would be to change the architecture to not rely on this timestamp. Instead uses something else for syncing etags for example. The draft for api v2 makes use of that concept but was never implemented.

Unfortunately this app is not backed up by an active development team but is more like a side project. So changes like this are very difficult.
We are also not related to the Nextcloud company in any way. We are just part of the community.

[wonderfulShrineMaidenOfParadise]

    location ~ \.php(?:$|/) {
        fastcgi_split_path_info ^(.+?\.php)(/.*)$;
        set $path_info $fastcgi_path_info;

        try_files $fastcgi_script_name =404;

        include fastcgi_params;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        fastcgi_param PATH_INFO $path_info;
        fastcgi_param HTTPS on;

        fastcgi_param modHeadersAvailable true;         # Avoid sending the security headers twice
        fastcgi_param front_controller_active true;     # Enable pretty urls

        fastcgi_pass php.loadbalancer.example.com:9000;

+       location ~ /index\.php/apps/news {
+               fastcgi_pass php64.loadbalancer.example.com:9000;
+       }

        fastcgi_intercept_errors on;
        fastcgi_request_buffering off;
    }

Currently I am trying this. Should be enough for News.