What's an ideal project structure for a Golang web service?

This page summarizes the projects mentioned and recommended in the original post on /r/golang

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • golang-standards/project-layout

    Standard Go Project Layout

  • 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"?

  • pocketbase

    Open Source realtime backend in 1 file

  • - https://github.com/pocketbase/pocketbase

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
  • memphis

    Memphis.dev is a highly scalable and effortless data streaming platform

  • - https://github.com/memphisdev/memphis

  • Mattermost

    Mattermost is an open source platform for secure collaboration across the entire software development lifecycle..

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts