https://github.com/caknoooo/quliku-backend-api

This repository is useful for making APIs for quliku applications based on Android, later this application will be used to carry out ITS Youth Technopreneur (IYT) activities
https://github.com/caknoooo/quliku-backend-api

clean-architecture gin golang gorm rest-api

Last synced: 4 days ago
JSON representation

This repository is useful for making APIs for quliku applications based on Android, later this application will be used to carry out ITS Youth Technopreneur (IYT) activities

• Host: GitHub
• URL: https://github.com/caknoooo/quliku-backend-api
• Owner: Caknoooo
• License: mit
• Created: 2023-07-21T00:42:38.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2023-08-31T09:21:11.000Z (over 1 year ago)
• Last Synced: 2024-11-02T00:21:46.540Z (about 2 months ago)
• Topics: clean-architecture, gin, golang, gorm, rest-api
• Language: Go
• Homepage:
• Size: 158 KB
• Stars: 1
• Watchers: 1
• Forks: 0
• Open Issues: 6
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Golang 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

## Layers 🔥

- **Domain Layer:** This layer contains the core business definitions of the application. It is the innermost layer and does not depend on any other layers. It includes entities, business rules, and repository interfaces that will be implemented in the infrastructure layer. 

- **Use Case Layer:** This layer holds the business logic specific to use cases in the application. Use cases provide operations and interactions between entities in the domain layer. Use cases do not depend on implementation details in the infrastructure layer.

- **Delivery Layer:** This layer is responsible for receiving and delivering data to and from the application. It typically consists of APIs, controllers, and presenters. This layer acts as the interface to interact with the outside world and can take input from users or deliver output to users.

- **Repository Layer:** This layer is responsible for implementing the repository interfaces defined in the domain layer. Repositories are used to access and store data from the storage (database, cache, APIs, etc.). This layer serves as a bridge between the domain layer and the infrastructure layer.

- **Infrastructure Layer:** This layer contains the technical details and implementation of the technologies used in the application, such as databases, networking, data storage, and external APIs. This layer depends on other layers and is used to implement the technical components required by the application.

## How To Use?