That should be completely fine. HTTP.jl can handle multiple simultaneous requests without problems.
However, given that you plan to use pods and containers, there is one issue which you will likely run in to: time to first response. Although Julia compilation keeps getting faster by optimizations in the core language and by optimizations of packages, the time to first response is longer than you would have in Go.
But, this of course, depends a bit on what you need. If you don’t mind that it takes pods a few seconds to minutes to start, then it’s all fine. Otherwise, you can try to reduce the time to first response via PackageCompiler.jl. A newer and even easier approach is via precompilation. It isn’t in the docs of SnoopCompile.jl yet, but there is an explanation by Tim Holy at Improve time-to-first-read via precompile + despecialization by quinnj · Pull Request #875 · JuliaData/CSV.jl · GitHub. Basically, with precompilation, Julia will precompile many core methods during package installation. So, if you do that inside a Docker build, then compilation should be quite fast for subsequent starts + runs of Julia, because the important execution paths are already compiled.