# New guy NGINX questions

**URL:** <https://community.nginx.org/t/new-guy-nginx-questions/6450>\
**Category:** General Discussion\
**Tags:** general-discussion, load-balancer, networking, config, web-server\
**Created:** [August 31, 2025, 4:29pm UTC](https://community.nginx.org/t/new-guy-nginx-questions/6450 "2025-08-31T16:29:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Akil\_Mieres](https://drob5swvtjqxg.cloudfront.net/user_avatar/community.nginx.org/akil_mieres/32/2951_2.png) [@Akil\_Mieres](https://community.nginx.org/u/Akil_Mieres)\
**Post date:** [August 31, 2025, 4:29pm UTC](https://community.nginx.org/t/new-guy-nginx-questions/6450/1 "2025-08-31T16:29:47Z")

</div>

Ok so the truth is I encountered nginx randomly. Visited freeeth.in and found the default site.

Ye old curiousity was peaked. So here I am.

What do you need to run nginx?

Am I am right to suppose it is more than an http-server?

How strong is it WIFI support?

Is the data access layer robust?

These types of questions that an old dude would ask?

---

<div class="post-metadata">

**Author:** ![davemc](https://drob5swvtjqxg.cloudfront.net/user_avatar/community.nginx.org/davemc/32/24_2.png) [@davemc](https://community.nginx.org/u/davemc)\
**Post date:** [September 4, 2025, 4:44pm UTC](https://community.nginx.org/t/new-guy-nginx-questions/6450/2 "2025-09-04T16:44:26Z")

</div>

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](https://github.com/nginx/nginx) 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)](https://nginx.org/en/)**. 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.

---

<div class="post-metadata">

**Author:** ![Akil\_Mieres](https://drob5swvtjqxg.cloudfront.net/user_avatar/community.nginx.org/akil_mieres/32/2951_2.png) [@Akil\_Mieres](https://community.nginx.org/u/Akil_Mieres)\
**Post date:** [September 4, 2025, 7:50pm UTC](https://community.nginx.org/t/new-guy-nginx-questions/6450/3 "2025-09-04T19:50:13Z")

</div>

Thanks guy,

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.

Thanks.