Standard Package Layout
Vendoring. Generics. These are seen as big issues in the Go community but there’s another issue that’s rarely mentioned — application package layout. Every Go application I’ve ever worked on appears to have a different answer to the question, how should I organize my code? Some applications push everything into one package while others group by type or module. Without a good strategy applied acros
Challenge to Advanced API Architecture in Go
The presentation slides on golang.tokyo#9 by @__timakin__
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
http://idiomaticgo.com/post/best-practice/server-project-layout/
http://idiomaticgo.com/post/best-practice/accept-interfaces-return-structs/
- YouTube
