What you need to know when creating a web service in a compiled language?

Question

go

Good afternoon, dear, the situation is as follows, I want to write a web service on compiled Go.
Previously, I worked only with interpreted languages, and then I had a question about what to consider when developing in a compiled language.
What should not be done, and what should be considered?
For example, I'm afraid that with a heavy load on the application, it may fall due to the fact that I did not take into account something, for example, the memory will overflow or something else (I honestly have little idea how a program in a compiled language works).
It’s easier with the interpreted one, I understand that the script worked and that’s it, but here it turns out the program is always in operation.
I hope I explained it more or less clearly, thanks in advance to everyone for the advice.

Answer 1

no, it's not like that,
no one bothers to drive written in interpreted languages ​​forever, not to run on each separate request,
no one bothers to restart written in compiled language for each request. moreover, it will even be faster than with an interpreted language.
pay attention to design.
if you apply the same approaches as for languages ​​with dynamic typing, Go will seem very inconvenient.
as soon as you discover that you need type casting or reflection here and there, it means that you designed it wrong, designed it the way you are used to doing in languages ​​with dynamic typing.
anything can fly. both interpreted and compiled.
if you need increased reliability, the launch environment should immediately restart the process. or generally have several processes running at the same time - spare and main, and balance requests between them. this applies to both compiled and interpreted languages.

Answer 2

Judging by your level (only based on the question), there will be no fundamental difference in development for you.
By and large, it is the same with the interpreted one: the compiled program is already machine instructions right away, and the interpreter spends time turning your code into machine instructions when it runs and first reads the code. For lovers of precise formulations, I will make a reservation right away - the explanation is "on the fingers."