Download
At The New York Times, our development teams have been adopting the Go programming language over the last three years to build better back-end services. In the past I’ve written about using Go for Elastic MapReduce streaming. I’ve also talked about using Go at GothamGo for news analysis and to improve our email and alert systems at the Golang NYC Meetup. We use Go for a wide variety of tasks, but the most common use throughout the company is for building JSON APIs. When we first began building APIs with Go, we didn’t use any frameworks or shared interfaces. This meant that they varied from team to team and project to project with regard to structure, naming conventions and third-party tools. As we started building more and more APIs, the pains of microservices started to become apparent. The config package provides a set of common, composable structs for working with tools common to the technology currently at The New York Times.
Features
- It’s meant to be a catchall struct that most applications should be able to use
- Config also contains a set of functions to help populate data into config types from JSON files
- The server package contains the bulk of the toolkit
- It provides a set of interfaces that define how a server and service should look and interact with one another starting with the Server interface
- The Server implementation is in charge of providing health checks, monitoring, logging, graceful shutdowns and hooks for adding in middleware handlers for any registered services
- Servers are meant to host services that (at a very minimum) must implement the Service interface
Project Samples
