Golang Boilerplate

The project should;

• be as explicit as possible
• use interfaces as little as possible
• easy to understand

Why only one service?

• less interfaces
• import cycles

Why only one storage?

• less interfaces

Run

To start watching your files for modification;

$ make start-deps
$ make

Dependencies

MySQL and Memcache

pkg/entity or pkg/iface was changed?

$ make gen

./schema.graphql was changed?

$ make update-graphql-schema

ps; $ make will watch and run make gen and update-graphql-schema automatically