Show HN: A simple Go web server with logging, tracing, health check

Re:Show HN: A simple Go web server with logging, tracing, he... by rcarmo on Sunday January 07, 2018 @12:37PM (#16091691)

I understand that, which is why I said "ORM(ish)". But a back-office scaffolding would go a long way to move some of us off of Django.

[ Parent | on HN ]

Re:Show HN: A simple Go web server with logging, tracing, he... by y4mi on Sunday January 07, 2018 @12:47PM (#16091736)

Why do you want to move off of Django?

[ Parent | on HN ]

Re:Show HN: A simple Go web server with logging, tracing, he... by rcarmo on Sunday January 07, 2018 @12:52PM (#16091751)

Because we're all using Go for other projects (even if piecemeal) and would like to build the entire project in a single language.

[ Parent | on HN ]

Re:Show HN: A simple Go web server with logging, tracing, he... by bsaul on Sunday January 07, 2018 @02:29PM (#16092184)

i personaly only would use go for very technical, low-level middlewares (as in, just above the OS layer) involving networks.

The good side to it being simple to understand and maintain is that you won't pay a lot of debt if you're adding it to your stack.

There isn't a single language that fits all use case perfectly anyway, so we'd have to just go to the "best tool for the job" approach in the meantime.

[ Parent | on HN ]

Re:Show HN: A simple Go web server with logging, tracing, he... by sd8dgf8ds8g8dsg on Sunday January 07, 2018 @08:57PM (#16094084)

> i personaly only would use go for very technical, low-level middlewares.

Care to extend upon why you don't feel go is a good fit for other programming?

[ Parent | on HN ]