A real-world backend API example built with Go, Fiber, Gorm, and Swagger, following the RealWorld specification.
Golang Fiber RealWorld Example App is a production-style backend API implementation built with the Go programming language and the Fiber web framework. It follows the RealWorld API specification to demonstrate common backend development patterns like CRUD operations, authentication, and API documentation. The project serves as a practical reference for developers learning how to build scalable and maintainable Go-based web services.
Go developers, especially those new to the Fiber framework, looking for a real-world example of building a full-featured backend API. It's also useful for developers implementing the RealWorld specification or seeking best practices in Go web development.
It provides a complete, well-structured example that adheres to community best practices, integrates modern tools like Swagger and Docker, and implements a standardized API spec, making it an excellent learning resource and a solid starting point for new projects.
Example real world backend API built with Golang + Fiber + Gorm + Swagger
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Follows Go and Fiber community style guides, providing a clean, maintainable codebase that serves as a learning resource for production-ready patterns.
Includes Swagger UI for interactive API exploration and testing, making it easy to understand endpoints without external tools.
Comes with Docker support and a start.sh script for quick containerization, allowing easy testing and deployment as shown in the README.
Features a full test suite runnable with 'go test ./...', ensuring reliability and correctness for common backend operations.
Requires Docker, docker-compose, and specific Go environment variables, which can be cumbersome for developers unfamiliar with these tools.
The project is designed around the RealWorld API, limiting flexibility for custom API designs or features outside the spec.
Relies on Gorm for ORM and assumes a certain project structure, which might not align with teams using alternative libraries or architectures.