darius-khll / golang-developer-roadmap Goto Github PK

Should you add the rpcx framework in MicroServices/Frameworks?

rpcx is a rpc framework with many features.

https://github.com/smallnest/rpcx

Hello, it is suggested to add GUI related information on the learning roadmap, thank you

Thank you

I did't improve this roadmap, but I translated it into Chinese. Here
Hope this will help more people.

I have been seeing such diagrams of developer roadmaps. How are such diagrams created? Where can I find more of such diagrams?

There could be a lot of approach to store your configuration to some file such as JSON, YAML, TOML, INI and etc. I wonder what's the proposed way to read/write configuration file in golang?

Since there is a GraphQL section already, I think its best to add some libraries to that section. More specifically these?

• gqlgen
• graphql-go

Would love to PR if need be.

Either the image shouldn't have a transparent background, or the text should all be in boxes/bubbles.

This is how it looks:

Beginning with golang

Hi, really like this project :)
Recommend to several projects we years already use in prod:

1. Config management: viper
2. WebServer - simple and very fast, on fasthttp base: atreugo
3. Distributed cache: aerospike
4. Log management system: graylog
5. Task scheduling: cron

Thank you!

Roadmap to becoming a Go developer in 2019

Should be...

Roadmap to becoming a Go developer in 2020

Hello, everyone. Cool project!

What do you think of adding a security path to the roadmap? I good start would be mentioning gosec. 🙃

For example, Staffjoy is an awesome project based on golang.
Maybe we can add it to a node ‘Project’

Just like this:

16. Project

• Staffjoy

What do you think of it?

I think you refer to wrong the HTTP client Heimdall. Should I change heimdall/heimdall to gojek/heimdall ?

GLog is a fatally flawed package, and should never be used.

In the Logging -> Distributed Tracing branch, Open Telemetry should be added alongside Jaeger

https://opentelemetry.io/docs/

From their doc : OpenTelemetry is a set of APIs, SDKs, tooling and integrations that are designed for the creation and management of telemetry data such as traces, metrics, and logs. The OpenTelemetry documentation is intended to broadly cover key terms, concepts, and instructions on how to use OpenTelemetry in your software.

They provide library for instrumentation and have the advantage to have implementation in multiple language which help in maintaining application in heterogeneous environments

Jaeger is also planning to get a closer integration with Open Telemetry (see https://www.jaegertracing.io/docs/1.21/opentelemetry/ )

road map not existed and download error

感觉缺少客户端侧负载均衡组件(独立于微服务框架的负载均衡)，类似java的Ribbon这样的组件

Change 2021 to 2023, add some new docs as well as some youtube tutorial for beginners

斯德哥尔摩

I think this roadmap should include profiling with pprof relatively early on.

Already have a PR ready, but I figured I would ask for your approval first 😄

Dockertest is a project developed to make Go integration tests really easy with Docker.
It is really popular on github, so I thought it might be a good addition to this list, let me know what you think.
Even Google is using it for some of their projects.

Docker is the perfect system for running unit tests as you can spin up containers in a few seconds and kill them when the test completes.
The Dockertest library provides easy to use commands for spinning up Docker containers and using them for your tests.+
Use Docker to run your Go language integration tests against third party services on Microsoft Windows, Mac OSX and Linux!

[disclaimer: i work for ory]

I just stumble upon your developer roadmap, as a newbie, I would like to know why you suggesting echo as framework of choice, since most of golang dev I met/talked to prefer no framework so they cannot help explain it.

I'm coming from PHP and Python so community already have general consensus on what framework to use, even PHP community basically advise to start new project using framework mainly due to possible security issue with no framework implementation.

Also some description on other decision would be great.

Could I translate it into Vietnamese?

Fiber is a great framework, simple, good documentation, good team, blazing fast (tested in local environment, production havent yet)

https://github.com/gofiber/fiber

LiteDB is a .NET-only project

关系数据库必会为什么不是MySQL

Hi, Maybe it's not a good place for asking such question，If it's not right place here Please let me know or you can close or delete it

How do you create this roadmap png ? maybe we could add more info on this roadmap tree
Do you have plan to do that?

Add RPC framework and specifically gRPC. It's very excellent ecosystem with Go.

https://github.com/grpc-ecosystem/awesome-grpc#lang-go

不要卷

Life is short, I tend to Golang!

little typo in go patterns structurul -> structural

While Dep was the official experiment, developers new to Go are encouraged to use Go modules instead since they are part of the official toolchain now.

I think it's time we stop recommending Dep to new developers and stick with the official standard.

What a fantastic project for me. 😁

2021 is coming soon. Will the author update the project? 😏

The logging topic structure shown in the diagram does not match what is in the readme. I believe it should start at the Logging node and not at the Log Frameworks node.

Not sure how to contribute or if the topics are already covered.

Noting them down in case some one is interested.

• Web : Gorilla toolkit
• DB: bolt DB
• DB Migration
• CLI tools: Cobra
• CLI Tools: cli
• Cache: LRU Map
• Mocking: counterfeiter
• Monitoring: prometheus

Hi there

Observability is a must have today, maybe we can have a Observability / Telemetry path to the roadmap?

I think future will be https://opentelemetry.io/, but there are a lot of framework technology : https://radar.cncf.io/2020-09-observability

Any reason Gorilla Mux does not appear in the list of routers ?