This is the third in my series of posts showcasing how to use the “adapter pattern” in Go. If you missed the earlier entries in this series, you should take a look at Part 1 and Part 2. This is the third and likely final component of the series; I’m going to show how you can structure handlers on your HTTP server in a way that plays nice with the patterns described in the previous posts. The inspiration for this post comes from Mat Ryer’s talk here.

This is the second in my series of posts showcasing how to use the “adapter pattern” in Go. If you missed Part 1, be sure to check it out because we’re going to be building on that here. For this post I’m going to show how you can adapt routes on your HTTP server with middleware functions. The inspiration for this post comes from Mat Ryer’s middleware post here.

In the next couple posts I’m going to show how to use the “adapter pattern” in Go. This is very handy pattern that allows for flexibility while keeping your APIs clean and readable. The inspiration for this post comes from a few blog posts I’ve read, but mainly Dave Cheney’s functional options post here.