These are slides from my talk at GothamGo 2018 in New York, NY. -- Building and launching an API in Go is great. Maintaining, not so much. I’ll review strategies for testing and versioning your Go API.

1. Future-proof your Go API
@stevekaliski

2. Overview
1. Introductions
2. “Future-Proof”
3. Testing
4. Versioning

3. 👋 Hi!

4. Future-proof?

5. Future-Proof
- Application
- Programming
- Interface

6. Future-Proof
- Application
- Programming → Less maintenance
- Interface → Increased stability

7. Why Go?
- Standard library (net/http, testing)
- Type + Interfaces
- Go Community + API Frameworks

8. Testing

11. net/http/httputil
func DumpResponse(resp *http.Response, body bool) ([]byte, error)

12. abide
func AssertHTTPResponse(t *testing.T, id string, w *http.Response)
type Assertable interface {
String() string
}

18. Testing - Summary
- net/http(/httputil, /httptest) = 👍
- Integrate into existing testing workflow = 👍
- httputil.DumpResponse as catchall = 👍
Future Proof = observability into interface

19. Versioning

21. pinned
type Version
type Change
type Versionable interface {
Data() map[string]interface{}
}
func Apply(v *Version, obj Versionable)

27. Versioning - Summary
- Use `Interface` to support any object = 👍
- Integrate into testing for observability = 👍

28. Thanks!
● twitter.com/stevekaliski
● github.com/sjkaliski
● sjkaliski@gmail.com

29. Resources
- github.com/beme/abide
- github.com/sjkaliski/pinned
- github.com/sjkaliski/gotham-go-examples