Avatar Service for All using Golang
Users love avatars, and they love to customize them, which is why I wrote this simple service that easily creates custom avatars for any purpose. The service is light, uses S3 for storage, and can be run easily from a single binary file.
tl;dr; Check out the source code
Avatars are usually the last thought for most developers building an awesome product or service. And perhaps they should be. A lot of people just default to Gravatar or some other global service. And this is generally fine, at least at the beginning.
Users’ preferences towards avatars can vary greatly. What we discovered at When I Work is that some of our customers thought avatars to be just as important as our scheduling product. They didn’t fully understand how to use Gravatar, and support spent way too long explaining things to them.
That’s when we decided to write an avatar service (originally in PHP). We architected it outside the main application and just communicated through standard HTTP.
After initially writing the service in PHP, we realized that the load required more servers than we wanted to use (or pay for). And given that the service itself is fairly simple, it made a lot of sense to write it in Go.
Golang is a great language for writing small and fast services. The spec is simple. Uploading the processing images is simple. Serving of images is a simple redirect. And all of them need to be fast!
In order to manage dependencies for things like image resizing and routing, we chose to use GoDep. This little script (which is also written in Go) helps to easily maintain all the requirements of the project, including checking them into the repository for version control.
Configuration should be simple. Using JSON and built in Go structs, it couldn’t be easier to access the settings. I’ve written about this before.
Simplicity & Flexibility
The service is simple and doesn’t pretend to force you to use it a certain way. Images are associated with a SHA1 hash, then uploaded to S3. There are plans to add additional storage providers, but S3 makes the most sense overall. Data related to the images is all stored in PostgreSQL.
You can hash anything, use that hash to upload, then retrieve it later. It’s really that simple.
Keeping simplicity in mind, authentication is handled using JWT. Setting a secret in the config file and using that same secret when generating your token will make uploads easy.
Using gocraft/web, we can easily authentication using middleware:
Make sure to check out the source code. It should be easy to setup and configure using the included scripts. Make sure to reach out or comment if you have questions or need help.