microservicebotexample
By polyapp-open-source
go-structure-examples
Examples for my talk on structuring go apps (by katzien)
Our great sponsors
microservicebotexample | go-structure-examples | |
---|---|---|
1 | 16 | |
- | 2,301 | |
- | - | |
- | 0.0 | |
- | 12 months ago | |
Go | ||
- | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
microservicebotexample
Posts with mentions or reviews of microservicebotexample.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-08-26.
go-structure-examples
Posts with mentions or reviews of go-structure-examples.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-29.
- How often do you use OOP design patterns while writing Go?
-
Hexagonal architecture and mocking
I have a question, I am trying out hexagonal architecture for one of my projects trying to follow this repository example and I ran into a slight problem.
-
Extra tool using main applications Go Ent structure question
Just fyi, that repo is NOT considered standard, and in fact, is often advised against. The structure of your code should depend on its complexity and how interoperable with other projects you need/would like it to be. I suggest watching this talk on structuring your code and taking a look at this companion repo to decide which will be the best way to structure your code, depending on your needs
-
Package Organization Approaches in Go
Kat Zien's excellent talk, presentation and code samples can be found here.
-
Go package&filename convention question from a Java developer
Thanks for the video, I'll take a look at it. And I checked the repo, I liked how the new is structured: https://github.com/katzien/go-structure-examples/tree/master/new
-
Next month I'll start working at a company as a Backend Developer and will be mostly using Go. How can I better prepare myself?
So here’s where I normally tell people to start off: check out this video and this repo in regards to the main 6 ways of architecting your Go applications.
-
how to structure a project?
Watch this and give this repo a look.
-
DDD file structure & cyclic dependencies
Am I completely fumbling it by approaching this the wrong way & if so what should I do differently? I have searched a few repos like this which redefines the same entity in multiple places which I feel is a violation of some sort, and this which the author had to resort to moving some files outside to overcome a circular dependency (see comments inside their handling.go file).
-
Is there any conventionally accepted repo that is representative of well designed go code ?
Really surprised I haven’t seen katzien/go-structure-example and her GopherCon 2018 talk about structuring your Go projects mentioned yet
-
Building a REST API with GO, Gin framework, and GORM.
Let's agree to leave the MVC model for OO languages. A better architecture would be something like katzien/go-structure-examples
What are some alternatives?
When comparing microservicebotexample and go-structure-examples you can also consider the following projects:
krok - The main server of the hook management system
fx - A dependency injection based application framework for Go.