What problems can there be when moving a server from ARM to x86?

Question

linux

I apologize if I'm asking too obvious and stupid things, don't kick too much.
What problems can there be if, for example, I, in the old fashioned way, will cut projects on a mini-PC at home (don't ask why), and then deploy the project on a normal hosting ??

Offtopic: just once (due to lack of practice) I encountered incompatibility, but not because of hardware - it was not possible to teach PHP to pull out previews from PDF on the production server, because there was another version of CentOS.

Answer 1

Anything.
Formally, there are no problems for high-level languages.
In fact, anything can come out, anywhere. Or maybe not get out.
It's easy to check.
The most likely place for jambs is in extensions (written in C, as a rule).
The PHP parts shouldn't be a problem.

Answer 2

If you do not use anything iron-specific, then none.
Well, you did not specify what kind of project you are working on, OS on ARM and x86.

Answer 3

The 21st century is in the yard, why is there such an urgent need for an ARM calculator?
Problems may be due to weapons. Not every software is compiled for ARM or configured differently.
Try. But I wouldn't risk it if the stack is exotic or close to it.

Answer 4

Well, the main problems are due to "dirty hacks" like assumptions about the size of variables in bytes, about byte order in a number, about floating point formats. Usually gets out in C-programs; in languages ​​like Python, PHP, Perl, this happens less often, but with diligence, you can also fly in. into problems. And Java was originally honed for standard execution everywhere and always - however, this was not completely successful, but there the likelihood of incompatibility is minimal.
The most common problems are when changing the bit depth of the system - 32 or 64 bits (there are other bit depths, but these days they are very rare).
To get started - specify the development language.