This repository holds the Uber Go Style Guide, which documentspatterns and conventions used in Go code at Uber.

Style Guide

See Uber Go Style Guide for the style guide.

Translations

We are aware of the following translations of this guide by the Go community.

• (Chinese): xxjwxc/uber_go_guide_cn
• (Korean): TangoEnSkai/uber-go-style-guide-kr
• (Japanese): knsh14/uber-style-guide-ja
• Traduccin al Espaol (Spanish): friendsofgo/uber-go-guide-es
• (Thai): pallat/uber-go-style-guide-th
• Traduo em portugus (Portuguese): lucassscaravelli/uber-go-guide-pt
• Tumaczenie polskie (Polish): DamianSkrzypczak/uber-go-guide-pl
• (Russian): sau00/uber-go-guide-ru

If you have a translation, feel free to submit a PR adding it to the list.

The Algorithms - Go

Algorithms implemented in Go (for education)

The repository is a collection of open-source implementation of a variety of algorithms implemented in Go and licensed under MIT License.

Read our Contribution Guidelines before you contribute.

List of Algorithms

See our directory.

Clean Go Code

Preface: Why Write Clean Code?

This document is a reference for the Go community that aims to help developers write cleaner code. Whether you're working on a personal project or as part of a larger team, writing clean code is an important skill to have. Establishing good paradigms and consistent, accessible standards for writing clean code can help prevent developers from wasting many meaningless hours on trying to understand their own (or others') work.

We dont read code, we decode it Peter Seibel

As developers, we're sometimes tempted to write code in a way that's convenient for the time being without regard for best practices; this makes code reviews and testing more difficult. In a sense, we're encodingand, in doing so, making it more difficult for others to decode our work. But we want our code to be usable, readable, and maintainable. And that requires

go-clean-arch

Changelog

• v1: checkout to the v1 branch
  Proposed on 2017, archived to v1 branch on 2018
  Desc: Initial proposal by me. The story can be read here: https://medium.com/@imantumorang/golang-clean-archithecture-efd6d7c43047

• v2: checkout to the v2 branch
  Proposed on 2018, archived to v2 branch on 2020
  Desc: Improvement from v1. The story can be read here: https://medium.com/@imantumorang/trying-clean-architecture-on-golang-2-44d615bf8fdf

• v3: master branch
  Proposed on 2019, merged to master on 2020.
  Desc: Introducing Domain package, the details can be seen on this PR #21

Description

This is an example of implementation of Clean Architecture in Go (Golang) projects.

Rule of Clean Architecture by Uncle Bob

• Independent of Frameworks. The architecture does not depend on the existence of some library of feature laden software. This allows you to use such frameworks as tools, rather than having to cram your system into their limited constraints.
• Testable. The business rules can be tested without the

Awesome Go

Sponsorships

We have no monthly cost, but we have employees working hard to maintain the Awesome Go, with money raised we can repay the effort of each person involved! All billing and distribution will be open to the entire community.

A curated list of awesome Go frameworks, libraries and software. Inspired by awesome-python.

Contributing

Please take a quick gander at the contribution guidelines first. Thanks to all contributors; you rock!

If you see a package or project here that is no longer maintained or is not a good fit, please submit a pull request to improve this file. Thank you!

Contents

• Awesome Go

  • Audio and Music
  • Authentication and OAuth
  • Bot Building
  • Build Automation
  • Command Line
  • Configuration
  • Continuous Integration
  • CSS Preprocessors
  • Data Structures
  • Database
  • Database Drivers
  • Date and Time
  • Distributed Systems
  • Dynamic DNS
  • Email
  • Embeddable Scripting Languages
  • Error Handling
  • File Handling
  • Financial
  • Forms
  • Functional
  • Game Development

Standard Go Project Layout

Translations:

• - ???
• Franais
• Portuguese
• Espaol
• Romn
• Trke

Overview

This is a basic layout for Go application projects. It's not an official standard defined by the core Go dev team; however, it is a set of common historical and emerging project layout patterns in the Go ecosystem. Some of these patterns are more popular than others. It also has a number of small enhancements along with several supporting directories common to any large enough real world application.

If you are trying to learn Go or if you are building a PoC or a simple project for yourself this project layout is an overkill. Start with something really simple instead (a single main.gofile andgo.mod is more than enough). As your project grows keep in mind that it'll be important to make sure your code is well structured