How I Learned Generics in Go

1. automated-garden

   1 2 32 7.9 Go

   weather-based smart irrigation controller and backend

   

   When thinking about duplicated code in my automated-garden project, the first thing that comes to mind is all of my API handlers. The server side of this application implements a few straightforward CRUD APIs following RESTful principles. Each resource type implements handlers for the different HTTP verbs and mostly interacts with the storage layer. I created a very simple setup for the API handlers following this formula:

2. InfluxDB

   www.influxdata.com featured

   InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.

   

3. render

   2 3 320 2.0 Go

   easily manage HTTP request / response payloads of Go HTTP services (by go-chi)

   

   GET endpoints just use go-chi/render to create the HTTP response

4. hord

   3 2 16 7.7 Go

   Discontinued Manage data in Go with a simple key-value interface supporting various databases. [Moved]

   Determined to implement generics and delete some lines of code, I turned my sights to the storage layer of my application. I designed my storage around key-value pairs since I started by storing resources in YAML files. This eventually evolved to use madflojo/hord to interact with key-value data stores like Redis. The function to read a *pkg.Garden from storage looks like this:

Suggest a related project