文件列表:

config/
constants/
controller/
dto/
entity/
helpers/
middleware/
migrations/
repository/
routes/
service/
tests/
utils/
.env.example
.husky.toml
LICENSE
Makefile
go.mod
go.sum
main
main.go
railway.yml

# Golang Gin Gorm With Clean Architecture ## Introduction > Clean Architecture is an approach to organizing code in an application that focuses on separating responsibilities and dependencies between components. In the context of Golang, Clean Architecture refers to the application of Clean Architecture principles in developing applications using the Go programming language. Clean Architecture proposes a structured application design with several layers that have clear and isolated responsibilities. Each layer has a specific role and boundaries. Here are some common layers in Golang Clean Architecture ## Directory / Layers - **Config** is aims to be directly related to things outside the code. An example is a database, etc. Configuration files play a crucial role in customizing the behavior of software applications. A well-structured config file can simplify the process of fine-tuning various settings to meet specific project requirements - **Constants** constant is a directory that deals with things that cannot be changed, in other words it is always constant and is usually called repeatedly - **Middleware** is an intermediary layer that serves to process and modify HTTP requests as they pass through the server before reaching the actual routes or actions. Middleware can be used to perform various tasks such as user authentication, data validation, logging, session management, response compression, and many more. It helps separate different functionalities within the API application and enables consistent processing for each incoming HTTP request. - **Controller** is a component or part of the application responsible for managing incoming HTTP requests from clients (such as browsers or mobile applications). The controller controls the flow of data between the client and the server and determines the actions to be taken based on the received requests. In other words, a controller is a crucial part of the REST API architecture that governs the interaction between the client and the server, ensuring that client requests are processed correctly according to predefined business rules. - **Service** refers to a component responsible for executing specific business logic or operations requested by clients through HTTP requests. The service acts as an intermediary layer between the controller and data storage, fetching data from storage or performing the relevant business operations, and then returning the results to the controller to be sent as an HTTP response to the client. The significance of service in REST API architecture is to separate the business logic from the controller, making the application more modular, testable, and adaptable. In other words, service enable the separation of responsibilities between receiving HTTP requests (by the controller) and executing the corresponding business actions. This helps maintain clean and structured code in the development of RESTful applications. - **Repository** is a component or layer responsible for interacting with data storage, such as a database or file storage, to retrieve, store, or manage data. The repository serves as a bridge between service and the actual data storage. The primary function of a repository is to abstract database or storage-related operations from business logic and HTTP request handling. In other words, the repository provides an interface for accessing and manipulating data, allowing service to focus on business logic without needing to know the technical details of data storage underneath. In the architecture of a REST API, the use of repositories helps maintain separation of concerns between different tasks in the application, making development, testing, and code maintenance more manageable. - **Utils** is short for "utility functions" or "utility tools." It refers to a collection of functions or tools used for common tasks such as data validation, string manipulation, security, error handling, database connection management, and more. Utils help avoid code duplication, improve code readability, and make application development more efficient by providing commonly used and reusable functions. ## Prerequisite - Go Version ``>= go 1.20`` - PostgreSQL Version ``>= version 15.0`` ## How To Use ``` 1. git clone https://github.com/Caknoooo/golang-clean-template.git 2. cd golang-clean-template 3. cp .env.example .env 4. configure .env with your postgres DB_HOST = localhost DB_USER = postgres DB_PASS = DB_NAME = DB_PORT = 5432 5. Open terminal, follow the steps below: - if you haven't downloaded postgres, you can download it first - Run -> psql -U postgres - Run -> Create database according to what you put in .env - \c (your database) - Run -> CREATE EXTENSION IF NOT EXISTS "uuid-ossp" - Run -> Exit 6. go run main.go ``` ## What did you get? If You using my Template. You get some endpoints that I have set up and an architecture that is ready to go https://documenter.getpostman.com/view/29665461/2s9YJaZQCG 

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：