cadey
/
route
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

README: move doc/README here

This commit is contained in:
Cadey Ratio 2017-12-15 12:59:26 -08:00
parent 46397943f6
commit a40613078e
2 changed files with 22 additions and 23 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
README.md
View File

@ -1 +0,0 @@
./doc/README.md

22
README.md Normal file
View File

@ -0,0 +1,22 @@
# Route
Route is a load balancer that has backends connect to the load balancer instead
of the load balancer connecting to backends. This model allows networks to be
vastly simplified, no longer having to bring in consul or another consensus layer,
no more configuration generation.
Project Stability: Alpha
This project is a passion project, as such excuse the atypical setup for everything.
If you have ideas on how to improve things, please open an issue, comment on existing
issues or hit me up in a private message somewhere. I want route to be the easiest
possible way to host services of all sizes.
Constraints I am putting on myself right now:
- Use Go as much as possible and where it makes sense use other tools
- Create solutions using experience from the "old way" of doing things to categorically eliminate problems
- Make solutions robust and fault-tolerant wherever possible as soon as possible
- Don't waste resources if you don't have to
- Always clean things up eventually
- If you have to fail, fail loudly
- Don't be too clever

22
doc/README.md
View File

@ -1,22 +0,0 @@
# Route
Route is a load balancer that has backends connect to the load balancer instead
of the load balancer connecting to backends. This model allows networks to be
vastly simplified, no longer having to bring in consul or another consensus layer,
no more configuration generation.
Project Stability: Alpha
This project is a passion project, as such excuse the atypical setup for everything.
If you have ideas on how to improve things, please open an issue, comment on existing
issues or hit me up in a private message somewhere. I want route to be the easiest
possible way to host services of all sizes.
Constraints I am putting on myself right now:
- Use Go as much as possible and where it makes sense use other tools
- Create solutions using experience from the "old way" of doing things to categorically eliminate problems
- Make solutions robust and fault-tolerant wherever possible as soon as possible
- Don't waste resources if you don't have to
- Always clean things up eventually
- If you have to fail, fail loudly
- Don't be too clever