How sdshah09/go-graphql works
Project Type and Purpose
• This is a backend GraphQL service written in Go, using gqlgen, that offers a single API layer with dual-database support (PostgreSQL and MongoDB) and includes logging (Fluent-Bit) and containerization (Docker/Docker-Compose).
• Its primary role is to expose CRUD operations on Patient entities via GraphQL, routing each request to the appropriate database based on an input flag.
File Structure Analysis
• Top level:
• server.go: entry point and HTTP server initialization.
• gqlgen.yml + graph/: GraphQL schema, generated models, resolvers.
• config/: centralized environment and app configuration.
• utils/: two subpackages (postgres, mongodb) encapsulating each database’s connection and CRUD logic.
• docker-compose.yml + Dockerfile: container orchestration.
• fluent-bit/: sidecar log collector configuration.
• tools.go, go.mod/go.sum: code tools and dependency management.
README Insights
• Describes features (dual DB support, GraphQL playground).
• Emphasizes environment-based configuration (.env) for database URIs.
• Points out code generation step via gqlgen.
• Illustrates database schemas and sample GraphQL queries/mutations.
a. Main Components:
• Client / GraphQL Playground (HTTP clients / frontend)
• GraphQL API Layer (server.go + gqlgen + resolvers)
• Configuration Manager (config package reading .env)
• Business Logic / Resolver Layer (graph/resolver.go)
• Database Adapter Layer (utils/postgres + utils/mongodb)
• Data Stores: PostgreSQL, MongoDB
• Logging Pipeline: Fluent-Bit sidecar, Docker logs folder
• Container Runtime: Docker Engine + Docker-Compose orchestration
b. Relationships & Data Flow:
1. Client → HTTP POST/GET → GraphQL API
2. GraphQL API → Resolver Logic → Database Adapter
3. Database Adapter → SQL driver or Mongo driver → Data Store
4. All components emit logs → Docker log driver → Fluent-Bit → target sink (e.g., stdout, external aggregator)
5. Configuration Manager feeds DB credentials & server port into API and adapters
c. Architectural Patterns & Principles:
• Layered architecture (API → service/resolver → data access layer)
• Dependency Injection via config structs
• Code generation (gqlgen) for type safety in schema
• Single-responsibility: each package has a clear concern
d. Key Technologies & Frameworks:
• Go modules, gqlgen for GraphQL
• PostgreSQL (via utils/postgres)
• MongoDB (via utils/mongodb)
• Docker & Docker-Compose for containerization
• Fluent-Bit for log aggregation