Questions
5 of 6
1How would you design a high-availability, horizontally scalable Go backend service?
2How do you build a basic HTTP server using only the standard library?
3How would you implement graceful shutdown for an HTTP server handling long-lived connections?
4How do you implement rate limiting in a Go API — per user, per IP, and globally?
5How would you implement middleware in Go using the standard library pattern vs a framework?
6What are the trade-offs between REST and gRPC for internal Go microservices?
golanggolang
Basics
Data Structures
Interfaces and Types
Concurrency
Memory Management
Error Handling
Packages and Modules
Web and API Development
Databases and Storage
Testing
DevOps and Deployment
Standard Library
05 / 06

How would you implement middleware in Go using the standard library pattern vs a framework?

Middleware in Go is a function that wraps an http.Handler and returns a new http.Handler. This pattern is the same whether using the standard library or frameworks like Gin and Echo.

Middleware pattern
Framework comparison
  1. 1

    Standard library: no dependencies, explicit, full control — preferred for simple services

  2. 2

    Gin: Use() method chains middleware; request context via gin.Context; fast router with params

  3. 3

    Echo: similar to Gin, cleaner API, built-in binder and validator

  4. 4

    Chi: 100% compatible with net/http; lightweight router with middleware support

  5. 5

    For most APIs: net/http + Chi or stdlib routing (Go 1.22) is sufficient without a full framework