There are countless examples of overlaps in software naming. I'm sure this isn't even the word with the most duplicates.

Also, the .sh does make this particular example at least slightly distinctive.

I'd just like to say how dispiriting I find this question considering I how envious of my friends $4k+ computer I was because it had 64mb of RAM and could play C&C Red Alert with absolutely no slowdown. Let that sink in...in the mid 90s, we comfortably fit a Windows GUI and a somewhat sophisticated game into 64mb of RAM and 20 years of "progress" later, we're asking what kind of special accommodations are necessary to handle HTTP requests with the same resources.

Note: It's an entirely reasonable question to ask, which makes it all the sadder.

A Node.js REST API can handle a significant volume of incoming requests with only 50mb-75mb of RAM. For reference here is a load test of handling around 75k-80k reqs/min using node.js containers deployed using Amazon ECS. Each node.js process is basically just doing CRUD operations, accepting incoming JSON, storing it in a database, fetching values back out of a database, and sending JSON back to clients. There is a bit of extra overhead from microservice HTTP fanout to other backend microservices, but the whole stack is very lightweight and 99% of requests are served in under 30ms.

As you can see this workload is only using about 6% of the available memory. For event loop driven systems like Node.js or Nginx, or Go the workload is almost always CPU bound not memory bound:

http://i.imgur.com/VCN5e21.png

I’m pretty sure most languages, even interpreted, can run at least small programs in 64MB. If you want to minimize memory usage at all costs, I think you’d want a non-GC compiled language (C(++), Swift and Rust come to mind).

It's rather common for managers to want simple, human-readable reports for information which is already exposed through a REST API.

Setting up a container with a cronjob that, once per day, executes a simple shell script which curls a REST endpoint, parses the relevant information, and sends an email out to a pre-defined mailing list or puts it to a slack channel... Yeah, that's pretty simple to pull off within that memory footprint.

Go is a good example - I have several services that consume ~20MB of RAM so no need for beefy boxes. Although that's why I also chose to use Kubernetes - extremely easy to pack a bunch of services.

I have a PHP based crawler scripts that range from 30 to 55 MB

nginx

I'm intrigued by network usage being "unlimited". Does this mean unlimited streaming of 10GB of video for a little over 3 USD/month?

They have per-second billing. Use it as serverless.

Kubernetes is not a provider, hyper.sh is.