Welcome to Gorox!

Gorox is an advanced Web server, App server, RPC framework, and proxy server. It can be used as:

• Web Server (HTTP 1/2/3, WebSocket, TLS, HWEB, FCGI, uwsgi, AJP)
• App Server for Go (Applications, Frameworks)
• RPC Framework for Go (HRPC, gRPC, Thrift)
• Web Proxy Server (HTTP, WebSocket, Tunneling, Forward, Reverse, Caching)
• Layer 4 Proxy Server (QUIC, TCP/TLS, UDP/DTLS)
• API Gateway
• Service Mesh
• ... and more through its highly extensible compoments design!

There is also a controller program called Myrox which is distributed with Gorox and can be used to manage your Gorox cluster optionally.

For more details about Gorox and Myrox, please see: https://gorox.io/ .

To be written.

Gorox should be working on these operating systems:

• Linux kernel >= 3.9
• FreeBSD >= 12.0
• Apple macOS >= Catalina
• Microsoft Windows >= 10

And these 64-bit CPU architectures:

• AMD64, also known as x64, x86-64, Intel 64
• ARM64, also known as AArch64
• RISCV64, also known as RV64, RISC-V 64
• Loong64, also known as LA64, LoongArch 64

Other platforms are currently not tested and probably don't work.

To start using Gorox, you can download the official binary distributions. If you need to build from source, please ensure you have Go >= 1.19 installed:

shell> go version

Then build Gorox with Go (if build failed, set CGO_ENABLED=0 and try again):

shell> go build

To run Gorox as a background daemon (if not, remove the "-daemon" option):

shell> ./gorox serve -daemon

To ensure the leader and the worker process are both started:

shell> ./gorox pids

Now visit http://localhost:3080 to check if it works. To exit server gracefully:

shell> ./gorox quit

For more actions and options, run:

shell> ./gorox -h

To install, move the whole Gorox directory to where you like. To uninstall, remove the whole Gorox directory.

Gorox is fast. You can use your favorite HTTP benchmarking tool (like wrk) to perform a benchmark against the following URLs:

• http://localhost:3080/hello
• http://localhost:3080/hello.html

Generally, the result is about 80% of nginx and slightly faster than fasthttp.

View Gorox documentation online:

• English version: https://gorox.io/docs
• Chinese version: https://www.gorox.io/docs

Or view locally (ensure your local server under hemi/gosites is started):

• English version: http://gorox.net:5080/docs
• Chinese version: http://www.gorox.net:5080/docs

By default, Gorox uses these dirs:

• apps/ - Place your Web applications,
• cmds/ - Place your auxiliary commands,
• conf/ - Place configs for Gorox and your commands,
• data/ - Place static shared files of your project,
• docs/ - Place docs of your project,
• exts/ - Place extended components written for your project,
• hemi/ - The Hemi Engine,
• idls/ - Place your Interface Description Language files,
• jobs/ - Place your Cronjobs written in Go and scheduled by Gorox,
• libs/ - Place libs written by you for your project,
• misc/ - Place misc resource of your project,
• srvs/ - Place your General Servers, like Chat server, SMS server, and so on,
• svcs/ - Place your RPC services,
• test/ - Place tests for your project.

After Gorox is started, 3 extra dirs are created:

• logs/ - Place running logs,
• temp/ - Place temp files which are safe to remove after Gorox is shutdown,
• vars/ - Place dynamic data files used by Gorox.

A typical deployment architecture using Gorox might looks like this:

            mobile  pc iot
               |    |   |
               |    |   |           public internet
               |    |   |
               v    v   v
             +------------+
+------------| edgeProxy1 |-------------+ gorox cluster
|            +--+---+--+--+             |
|    web        |   |  |       tcp      |
|      +--------+   |  +-------+        |
|      |            |          |        |
|      v           rpc         v        |
|   +------+        |       +------+    |
|   | app1 +----+   |   +---+ srv1 |    |
|   +------+    |   |   |   +---+--+    |
|               |   |   |       |       | stateless layer
|               v   v   v       v       |
|  +------+   +----------+  +--------+  |   +------------------+
|  | svc1 |<->| sidecar1 |  | proxy2 |--+-->| php-fpm / tomcat |
|  +------+   +----+-----+  +--------+  |   +------------------+
|                  |                    |
|                  v                    |
|  +------+   +----------+   +------+   |
|  | svc2 |<--+ sidecar2 |   | job1 |   |
|  +------+   +----------+   +------+   |
|                                       |
+-----------+------+---------+----------+
            |      |         |
            v      v         v
+---------------------------------------+
|     +------+  +-----+  +--------+     |
| ... | db1  |  | mq1 |  | cache1 | ... | stateful layer
|     +------+  +-----+  +--------+     |
+---------------------------------------+

In this typical architecture, with various configurations, Gorox can play ALL of the roles in "gorox cluster":

• edgeProxy1: The Edge Proxy, also works as an API Gateway or WAF,
• app1 : A Web application implemented directly on Gorox,
• srv1 : A TCP server implemented directly on Gorox,
• svc1 : A public RPC service implemented directly on Gorox,
• sidecar1 : A sidecar for svc1,
• proxy2 : A gateway proxy passing requests to PHP-FPM / Tomcat server,
• svc2 : A private RPC service implemented directly on Gorox,
• sidecar2 : A sidecar for svc2,
• job1 : A background application in Gorox doing something periodically.

The whole gorox cluster can alternatively be managed by a Myrox instance, which behaves like the control plane in Service Mesh. In this configuration, all Gorox instances in the cluster connect to Myrox and are under its control.

A Gorox instance has two processes: a leader process, and a worker process:

                  +----------------+         +----------------+ business traffic
         cmdConn  |                | msgConn |                |<===============>
operator--------->| leader process |<------->| worker process |<===============>
                  |                |         |                |<===============>
                  +----------------+         +----------------+

Leader process manages the worker process, which do the real and heavy work.

A Gorox instance can be controlled by operators through the cmdui interface of leader process. Operators connect to leader, send commands, and leader executes the commands. Some commands are delivered to worker through msgConn.

Alternatively, Gorox instances can connects to a Myrox instance and delegates its administration to Myrox. In this way, the cmdui interface in leader process is disabled.

Currently Github Discussions is used for discussing:

https://github.com/hexinfra/gorox/discussions

Gorox is originally written by Zhang Jingcheng [email protected]. You can also contact him through Twitter: @diogin.

The official website of the Gorox project is at:

• English version: https://gorox.io/
• Chinese version: https://www.gorox.io/

Gorox is licensed under a BSD License. See LICENSE.md file.

Gorox is hosted at Github:

https://github.com/hexinfra/gorox

Fork this repository and contribute your patch through Github Pull Requests.

By contributing to Gorox, you MUST agree to release your code under the BSD License that you can find in the LICENSE.md file.