Application platform powers Loadbalancer, Microservices and API Gateways
This project was started from ugly fun example.
But this project is not a simple HTTP load balncer. We dont need it. We need to balance our application payload.
So let we use somthing like a application bus to communicate with application logic.
Also there standard practice to use external crates(modules,libraries).
But lot of them suffer from overprogramming, not clear implementation of specifications and unnecessary extra functionality.
So i liked the starter point of project and i would like to use less external code in that project.
Because “less code” is mean less errors and faster executon, which is main goal.
See the Borderland Project Wiki for full documentation, examples, and operational details.
You may be looking for:
Make sure you have cargo
installed and run the command cargo run
to boot up the server.
Visit locahost:8080
from your browser.
Say hello world - visit localhost:8888/api/v1
Serve static files - visit localhost:8888/files/index.html
- this will serve the index.html
file from the www
folder in the repo root.
Place any other file inside www
and they can be served similarly (using the /files
prefix - this will be configurable by the user in future, just like in Apache and Nginx).
file
command)
$ab -n 5000 -kc 500 http://127.0.0.1:8000/
...
Requests per second: 14109.94 [#/sec] (mean)
Time per request: 35.436 [ms] (mean)
Time per request: 0.071 [ms] (mean, across all concurrent requests)
It’s sad (((
This work is licensed under the MIT license. See LICENSE for details.