golang-standards/project-layout

Standard Go Project Layout (by golang-standards)

Golang-standards/project-layout Alternatives

Similar projects and alternatives to golang-standards/project-layout

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better golang-standards/project-layout alternative or higher similarity.

golang-standards/project-layout reviews and mentions

Posts with mentions or reviews of golang-standards/project-layout. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-09-27.
  • Building RESTful API with Hexagonal Architecture in Go
    21 projects | dev.to | 27 Sep 2023
    I've been learning how to build web applications using different frameworks and languages for a while now, such as Laravel with its MVC architecture and Node.js following the 'Hapi.js Way'. As I'm trying to create a new portfolio project using Go, I found myself contemplating over the ideal project structure. I wanted something that not only aligns with the standard Go project layout, but also makes the code both easy to write and understand. That's when I stumbled upon the concept of Hexagonal Architecture, as showcased in Netflix's engineering blog. The idea of seamlessly swapping infrastructures with minimal code changes fascinated me, and I decided to implement it in my new project.
  • Idea of multiple directories
    2 projects | /r/golang | 1 Jul 2023
    I think this doc does a good job covering the design (unofficial) design guidance https://github.com/golang-standards/project-layout
  • go app project structure
    2 projects | /r/golang | 30 Jun 2023
    I try to follow this approach as well after trying the overly complicated https://github.com/golang-standards/project-layout.
    2 projects | /r/golang | 30 Jun 2023
    project-layout
  • Why no src directory?
    3 projects | /r/golang | 31 May 2023
    Why src directory? Git repos are for source code, such name is meaningless. For complex projects I prefer using standard go project layout. For single package or single command projects flat repo is OK.
  • Directory structure for a golang project
    3 projects | /r/golang | 20 May 2023
    Standard Go Project Layout
    3 projects | /r/golang | 20 May 2023
    The name of this project is misleading: https://github.com/golang-standards/project-layout/issues/185
  • What's an ideal project structure for a Golang web service?
    7 projects | /r/golang | 8 Apr 2023
    Regarding https://github.com/golang-standards/project-layout/issues/38 what exactly is meant by "part of the project structure is a bad practice ( like vendor or pkg directories, we have something called mods now"?
    7 projects | /r/golang | 8 Apr 2023
  • Does this project structure make sense?
    6 projects | /r/golang | 5 Apr 2023
    You can skip the top-level pkg — it’s not needed or recommended. +1 for Fx 🤗
  • A note from our sponsor - SonarQube
    www.sonarqube.org | 29 Sep 2023
    Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free. Learn more →

Stats

Basic golang-standards/project-layout repo stats
184
42,073
7.5
9 days ago
Static code analysis for 29 languages.
Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.
www.sonarqube.org