From Wikipedia, the free encyclopedia
I will be including references to these topics:
This reference is from a printed book on Mesos / Marathon, which isn't at all related to Docker: "Traefik is a load balancer, a.k.a. proxy, working on layer 7. It works on a very simple concept that has been around since Apache and PHP. Traefik parses HTTP requests and passes them to matching services. We can achieve similar functionality with Apache, nginx, or HAProxy, but only Traefik comes with built-in Marathon support" [1].
There have been books published on Kubernetes as well, which include similar references to Traefik:
"Traefik (pronounced Traffic) is a reverse HTTP proxy which has been designed to work from the ground up with container orchestration tools like Kubernetes. It not only provides load balancing but also supports basic HTTP authentication and SSL termination. To find out more about Traefik, see its website at https://traefik.io" [2]
"Traefik is a reverse proxy implemented in Go that can also function as an Ingress controller. It has a set of features and dashboards that are very developer-friendly." [3]
I also included references to books on Docker, which cover the subject of Traefik in-depth:
"Traefik is a fast, powerful, and easy-to-use reverse proxy. You run it in a container and publish the HTTP (or HTTPS) port, and configure the container to listen for events from the Docker Engine API ..." [4]
"Traefik is a cloud-native edge router and it is open source, which is great for our specific case. It even has a nice web UI that you can use to manage and monitor your routes. Traefik can be combined with Docker in a very straightforward way, as we will see in a moment." [5]
Traefik has also been the subject of independent reviews, ThoughtWorks Technology Radar reviewed Traefik in Nov. 2018, explaining in similar detail to the references I've mentioned above what the technology is, including mentions of other projects which are hosted on Wiki, and rated it as, "Worth exploring with the goal of understanding how it will affect your enterprise." [6] There are also reviews on g2crowd, and while standing alone I wouldn't suggest this implies notability, I believe it should be considered nevertheless. [7]
While I understand that a single mention in a book isn't considered notable, I am suggesting that combined with in-depth how-tos, non-trivial descriptions, and comparisons to other major projects which are active on this Wiki across several printed books with a diversity of subject matter should be considered for notability. This in addition to well over 100s of tutorials/blogs, independent reviews, videos, and tutorials, all of which have no connection to the publisher, should also be considered for notability. A simple google search "traefik tutorial" will unearth that maelstrom.
In summary, in addition to the above references, I strongly believe there was insufficient discussion on the subject of deletion, and I would argue the sole individual who voted for deletion, with a suggestion that this belongs on the Docker page, may not have been aware of how notable Traefik actually is and it's relevance to the entire web-application ecosystem and other projects including Nomad, Kubernetes, Mesos / Marathon, etc.
At a minimum, I'd like a copy of the article, with references, emailed to me - if possible. Thank you for your time. I'm looking forward to hearing your thoughts.
Kcmastrpc ( talk) 19:47, 6 June 2020 (UTC) reply
From Wikipedia, the free encyclopedia
I will be including references to these topics:
This reference is from a printed book on Mesos / Marathon, which isn't at all related to Docker: "Traefik is a load balancer, a.k.a. proxy, working on layer 7. It works on a very simple concept that has been around since Apache and PHP. Traefik parses HTTP requests and passes them to matching services. We can achieve similar functionality with Apache, nginx, or HAProxy, but only Traefik comes with built-in Marathon support" [1].
There have been books published on Kubernetes as well, which include similar references to Traefik:
"Traefik (pronounced Traffic) is a reverse HTTP proxy which has been designed to work from the ground up with container orchestration tools like Kubernetes. It not only provides load balancing but also supports basic HTTP authentication and SSL termination. To find out more about Traefik, see its website at https://traefik.io" [2]
"Traefik is a reverse proxy implemented in Go that can also function as an Ingress controller. It has a set of features and dashboards that are very developer-friendly." [3]
I also included references to books on Docker, which cover the subject of Traefik in-depth:
"Traefik is a fast, powerful, and easy-to-use reverse proxy. You run it in a container and publish the HTTP (or HTTPS) port, and configure the container to listen for events from the Docker Engine API ..." [4]
"Traefik is a cloud-native edge router and it is open source, which is great for our specific case. It even has a nice web UI that you can use to manage and monitor your routes. Traefik can be combined with Docker in a very straightforward way, as we will see in a moment." [5]
Traefik has also been the subject of independent reviews, ThoughtWorks Technology Radar reviewed Traefik in Nov. 2018, explaining in similar detail to the references I've mentioned above what the technology is, including mentions of other projects which are hosted on Wiki, and rated it as, "Worth exploring with the goal of understanding how it will affect your enterprise." [6] There are also reviews on g2crowd, and while standing alone I wouldn't suggest this implies notability, I believe it should be considered nevertheless. [7]
While I understand that a single mention in a book isn't considered notable, I am suggesting that combined with in-depth how-tos, non-trivial descriptions, and comparisons to other major projects which are active on this Wiki across several printed books with a diversity of subject matter should be considered for notability. This in addition to well over 100s of tutorials/blogs, independent reviews, videos, and tutorials, all of which have no connection to the publisher, should also be considered for notability. A simple google search "traefik tutorial" will unearth that maelstrom.
In summary, in addition to the above references, I strongly believe there was insufficient discussion on the subject of deletion, and I would argue the sole individual who voted for deletion, with a suggestion that this belongs on the Docker page, may not have been aware of how notable Traefik actually is and it's relevance to the entire web-application ecosystem and other projects including Nomad, Kubernetes, Mesos / Marathon, etc.
At a minimum, I'd like a copy of the article, with references, emailed to me - if possible. Thank you for your time. I'm looking forward to hearing your thoughts.
Kcmastrpc ( talk) 19:47, 6 June 2020 (UTC) reply

Videos

Youtube | Vimeo | Bing

Websites

Google | Yahoo | Bing

Encyclopedia

Google | Yahoo | Bing

Facebook