Some brief answers but glad to expand on anything. I certainly ask my share of old guy questions.
What do you need to run F5 NGINX?
To run NGINX, you need an OS (Linux is most common), a network stack, and a configuration file. It’s known for being lightweight and event-driven, and handling a high volume of concurrent connections. There is an open source version and a commercial version (F5 NGINX Plus).
Is it more than an HTTP server?
Yes. It can serve web pages; it is also a reverse proxy and load balancer (and more). Instead of exposing your application servers directly to the internet, you put NGINX in front of them. It routes traffic, caches content, and can distribute requests across multiple backend instances
How strong is its Wi-Fi support?
This is a networking layer concern, not an application-level one. NGINX doesn’t care how if the packets arrive.
Is the data access layer robust?
NGINX doesn’t have a traditional data access layer. It’s not a database; it’s a web server and a proxy. It can serve files from a file system, but it doesn’t handle database queries, transactions, or data persistence.
Sounds typical, except for the event driven part. Could probably use a delegate/call back dll structure to riggup an http endpoint and probably use it as a node for a number of things.
The wifi support at L4 is actually better than at L7.
Could always wrap that. This Signal hopping heifer lump is becoming a nuisance.
I,ll have to look into it sounds perfect for Gis or other such apps.
Such as EMR pollution protection node. But would need a Signal transmission dll to fine tune raw transmissions to avoid Ozone depletion dye to quantum based reactions.