7 ms·
>"Why Go saved my a* I'm not going to give you a lecture. Here are the concrete numbers: RAM — the real deal Node.js, on my latest version, was using 1.4 GB o
by peter_d_sherman 8d ago
>"Why Go saved my a*
I'm not going to give you a lecture. Here are the concrete numbers: RAM — the real deal
Node.js, on my latest version, was using 1.4 GB of RAM just to boot the app on one instance.
Go?
48 MB.
I'm not kidding. On the first test I ran, I launched a 15 MB Go binary on a t3.micro. The API responded in 20ms. I thought I'd measured wrong. I checked three times. It wasn't a mistake."
There is definitely something to be said for a self-contained high-performance server in 48 MB...