Best Practices for Structuring Large Go Projects?

  • There is no one-size-fits-all structure. Each project requires thoughtful consideration of its specific needs. I recently attended a presentation by an Ardan Labs representative discussing Domain-Driven Design, who emphasized that project structure should vary based on project requirements and team size. Ensure your chosen structure aligns with your specific goals and context.
  • For applications running on the same server, a single binary approach is appropriate. However, I believe there may be a misconception in the discussion. The fundamental consideration is whether to implement a monolithic or distributed system architecture.
  • I prioritize maintaining a minimal dependency footprint. It’s important to note that version consistency isn’t the critical factor—data consistency is what truly matters for system integrity.

And no tips considering Go for Tableau, whatever this is. Data is just data. always. :slight_smile:

1 Like