Go is a language designed for engineering teams. It's central themes are simplicity, readability, and maintainability. This talk will provide best practice real world advice for teams building projects in Go covering five areas; idiomatic code, package and api design, error handling, concurrency, and testing. 

内容大纲

Identifiers

1. Choose identifiers for clarity, not brevity
2. Use a consistent declaraton style

Package Design

1. A good package starts with its name An identifier’s name includes its package name Prefer lower case package names and import paths
2. Rather than nesting deeply, return early
3. Make the zero value useful
4. Eschew package level state. No package level variables. Avoid global side effects.

Project Structure

1. Consider fewer, larger packages Arrange code into files by import statements. Prefer nouns for file names. Eschew elaborate package hierarchies, resist the desire to apply taxonomy
2. Keep package main small as small as possible

API Design

1. Design APIs that are hard to misuse. Design APIs for their default use case.
2. Prefer var args to []T parameters
3. Let callers define the interface they require
4. Prefer streaming interfaces
5. Use type assertions for optional behaviour

Error handling

1. Elminate handling by eliminating errors
2. Only handle an error once

Concurrency

1. Never start a goroutine without when it will stop. When sending or receiving on a channel, consider what happens if the other party never receives the message
2. Keep yourself busy while waiting for a goroutine. or, do the work yourself.
3. Leave concurrency to the caller

Go is a language designed for engineering teams. It's central themes are simplicity, readability, and maintainability. This talk will provide best practice real world advice for teams building projects in Go covering five areas; idiomatic code, package and api design, error handling, concurrency, and testing. 

自从 2011年被捐献给Apache基金会到现在，Kafka项目已经走过了七个年头。从最早的“分布式消息系统”，到现在集成了分发、存储和计算的“流式数据平台”，Kafka经历了哪些挑战？又经过了什么样的演进变化？Kafka 社区踩过哪些“坑”？本次演讲将为你一一道来。

主要内容 & 听众收益

a. 从硬件的发展趋势，展现 Kafka 架构的演进过程。

b. 从Kafka开发和维护经验，分享分布式系统工程实践的通理。

c. 开源数据系统的开发经验，如何维护和发展一个开源社区。

自从 2011年被捐献给Apache基金会到现在，Kafka项目已经走过了七个年头。从最早的“分布式消息系统”，到现在集成了分发、存储和计算的“流式数据平台”，Kafka经历了哪些挑战？又经过了什么样的演进变化？Kafka 社区踩过哪些“坑”？本次演讲将为你一一道来。

主要内容 & 听众收益

a. 从硬件的发展趋势，展现 Kafka 架构的演进过程。

b. 从Kafka开发和维护经验，分享分布式系统工程实践的通理。

c. 开源数据系统的开发经验，如何维护和发展一个开源社区。