Swego
Swiss army knife Webserver in Golang. Keep simple like the python SimpleHTTPServer but with many features (by nodauf)
goapp
An opinionated guideline to structure & develop a Go web application/service (by bnkamalesh)
| Swego | goapp | |
|---|---|---|
| 3 | 11 | |
| 192 | 766 | |
| - | - | |
| 3.1 | 2.7 | |
| 8 months ago | 5 days ago | |
| Go | Go | |
| GNU General Public License v3.0 only | 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.
Swego
Posts with mentions or reviews of Swego.
We have used some of these posts to build our list of alternatives
and similar projects.
goapp
Posts with mentions or reviews of goapp.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-02-08.
-
A practical approach to structuring Golang apps
2022 update. At the time of writing this update, it's been over a year since I published this article. At the end of this article I promise a part two, which I must admit, will probably never come for a couple of reasons. I no longer use this structure (I still think this article gives people some help to get going, but would like to update it at one point. I suggest you checkout this repo. Secondly, in regards to integration testing, I've just relased a full-length article about it which you can find here.
- Calling Profesh Go developers for some suggestions on a good directory structure, architecture and design suggestion for a Go based backend API ?
- How to structure an API using Go?
-
A practical approach to structuring Golang applications
I wrote this article a year ago and there is much I would change about it today. I still post it because I think there are something to be learned from this, at least to get a end 2 end description of one way to structure Go applications. There are many other options, and today I would suggest that you check out this repository.
-
Would you recommend me (OR NOT) to use kataras/iris framework for prod???
Also regarding how you organise the code you could check out https://github.com/bnkamalesh/goapp
-
Show me your REST APIs 😊
I've been using https://github.com/bnkamalesh/webgo for all my projects. Also, I follow https://github.com/bnkamalesh/goapp to organize code
-
What is the best way to organize code within a Go project?
https://awesome-go.com is a good place for aggregated resources. Also regarding code organization, I've done something, which l follow till date, https://github.com/bnkamalesh/goapp
-
Project structure for Golang web server + react
I've been using this for a while now, (Goapp)[https://github.com/bnkamalesh/goapp]
-
Folder structure for a golang web application project with REST API
I've been using goapp for a long while now
-
"Packages as layers, not group" follow up to "Standard Package Layout""
in which case, you might like this one
What are some alternatives?
When comparing Swego and goapp you can also consider the following projects:
fileless-xec - Stealth dropper executing remote binaries without dropping them on disk .(HTTP3 support, ICMP support, invisible tracks, cross-platform,...)
modern-go-application - Modern Go Application example