Go Pointers: When I Don’t Use Interfaces (in Go)

Photo by Clément H on Unsplash

Level setting

Small interfaces

First-class functions

Other languages

A word of caution

Where I tend to use this

  1. It makes the choice to handle the request one way or another on the basis of the major protocol version.
  2. It may execute logic for proxying an HTTP/2 request.
  3. It may execute logic for proxying an HTTP/1.x request.

Conclusion

--

--

--

Kent is a senior engineer on the Azure Cloud Native Computing team at Microsoft, working primarily with Kubernetes and other open source projects.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

My spell-chekcer is dribing me carzy!

WAYS TO ADD CSS TO HTML

Desktop Flutter Apps

Fuzzy String Matching With Python

Build an Event Booking App (Practice)

Deleting a Leaf From a Tree Visually Explained

What is Programming?

NFTSCAN and Coinhub have reached a cooperation on NFT data

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Kent Rancourt

Kent Rancourt

Kent is a senior engineer on the Azure Cloud Native Computing team at Microsoft, working primarily with Kubernetes and other open source projects.

More from Medium

Use pprof to view go program stack traces

Golang Testify: require vs assert

Hacking sum types with Go generics

What’s so cool about golang