HN user

engine_y

119 karma
Posts1
Comments17
View on HN

Welp. We used it in prod for ~18 months or so but the experience was not something we'd repeat.

The configuration of Traefik, in our case, embedded in the docker-compose file was not clear. What was supposed to be a 'auto-detection' of services ended up looking like a hodge-podge of configs between several files.

The logging was sub-par - we couldn't properly debug issues.

And then we ended up migrating terminating HTTPS on AWS's ELB so the let's encrypt integration became not relevant which catalyzed us going back to nginx.

Well maybe it should be. I was thinking the same about languages which are better suited for data wrangling. But to me, the reason python is the DS language shows how good evolution is and survival of the fittest. You and I would probably argue that a DS language should have strong static typing but in nature what prevailed was the opposite. A nimble, easy, no fuss, comedy oriented named language.

I wonder what people here think. Would self serve BI work for something which is more context specific? So for example self serve BI for your own sales. What would it take? Why not?

I was bought my vegetables from a guy who used absolutly no insecticides or pesticides. It was really great. He had a pretty decent area of land where he grew a plethora of crops. He told me that sometimes some of the plants were eaten but he had others so it's fine. The vegetables were very tasty and fresh and we loved it. We were glad to pay a bit more for fresh and poison free stuff.

Unfortunately, after a year or so he went out of business because he let the insects eat his plants.

We've been using Traefik in prod for 2 years. While I used NGINX in the past, I decided to migrate to Traefik mainly because of the automatic let's encrypt integration. I am sorry for that decision. Traefik's documentation does not make sense to me or my team. It is finicky and misbehaves without proper logging. As an example - when I want to recreate the certificates - it fails sporadically leaving prod down for an indefinite amount of time.

We're moving back to NGINX.