How I write HTTP services after eight years.

Mat Ryer · 9 May 2018

How I write HTTP services after eight years.

Mat Ryer · 9 May 2018

(The coffee photo comes from Coffee Geek - who have a great blog for coffee lovers https://coffeegeek.tv/blog/)

An updated version is available

You can find the latest version of this article on the Grafana Labs blog: How I write HTTP services in Go after 13 years.


Learn more about what we're doing at Pace.

A lot of our blog posts come out of the technical work behind a project we're working on called Pace.

We were frustrated by communication and project management tools that interrupt your flow and overly complicated workflows turn simple tasks, hard. So we decided to build Pace.

Pace is a new minimalist project management tool for tech teams. We promote asynchronous communication by default, while allowing for those times when you really need to chat.

We shift the way work is assigned by allowing only self-assignment, creating a more empowered team and protecting the attention and focus of devs.

We're currently live and would love you to try it and share your opinions on what project management tools should and shouldn't do.

What next? Start your 14 day free trial to see if Pace is right for your team


First published on 9 May 2018 by Mat Ryer
#Golang #HTTP #WebServices

or you can share the URL directly:

https://pace.dev/blog/2018/05/09/how-I-write-http-services-after-eight-years.html

Thank you, we don't do ads so we rely on you to spread the word.

https://pace.dev/blog/2018/05/09/how-I-write-http-services-after-eight-years.html


You might also like:

Respond to Ctrl+C interrupt signals gracefully #Golang #Patterns

How code generation wrote our API and CLI #codegen #api #cli #golang #javascript #typescript

Why you shouldn't use func main in Go #Golang #Patterns

Subscribe:
Atom RSS JSON