go-backend-template
gofre
| go-backend-template | gofre | |
|---|---|---|
| 2 | 4 | |
| 44 | 17 | |
| - | - | |
| 0.0 | 10.0 | |
| almost 2 years ago | over 1 year ago | |
| Go | Go | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
go-backend-template
- Golang backend template
-
Clean Architecture based sample in Golang
I am new in Golang. I recently tried to write a clean architecture based project. The result is this sample: https://github.com/pvarentsov/go-backend-template. Hope someone will find it interesting. I'd be happy to get feedback.
gofre
-
Does Echo provide things Fiber doesn't?
Maybe you can take a look over my framework https://github.com/ixtendio/gofre which respects all the golang standards and has similar performance like echo.
-
Examples of Go Gin deviating from Standard Library
Maybe you can try https://github.com/ixtendio/gofre which is a web framework that respects the Golang standards, has a nice error management and in some cases performs better than Gin. On top of that the pattern matching is much richer and better than Gin or Echo
-
GoFre - a sweet web framework :)
Hi sikoyo, and thanks for your appreciation. If it will be to compare with other popular frameworks, not only with Echo, it will be like: 1. The programming model is simple and natural. For example a GoFre handler returns a response or an error. The response is an interface with 4 methods, compared with Echo which provides a Context (an interface with 55 methods :) ). Imagine if you want to extend Echo with response compression how simple it is? In GoFre just implement a new Response that wraps the original response. See this implementation https://github.com/ixtendio/gofre/blob/main/response/compress.go for example Gin, another framework uses the same concept like Echo :) but at least in their case the Context is not an interface but a structure which contains a lot of fields which should not be there. The same problem here, how easy is it to extend it for your needs? 2. Another difference is in patch matching. GoFre supports approximately the same path matching as the Java Spring framework. For example if you have the following patterns:
What are some alternatives?
go-clean-arch - Go (Golang) Clean Architecture based on Reading Uncle Bob's Clean Architecture
ladder - Selfhosted alternative to 12ft.io. and 1ft.io bypass paywalls with a proxy ladder and remove CORS headers from any URL
go-template - Go-template is an opinionated Hexagonal backend template written in GO.
casdoor - An open-source UI-first Identity and Access Management (IAM) / Single-Sign-On (SSO) platform with web UI supporting OAuth 2.0, OIDC, SAML, CAS, LDAP, SCIM, WebAuthn, TOTP, MFA and RADIUS [Moved to: https://github.com/casdoor/casdoor]
create-go-app - ✨ A complete and self-contained solution for developers of any qualification to create a production-ready project with backend (Go), frontend (JavaScript, TypeScript) and deploy automation (Ansible, Docker) by running only one CLI command.
sse - Server Sent Events server and client for Golang
migrate - Database migrations. CLI and Golang library.
blackbox - Black Box provides simple to use, extensible, and easily testable typesafe server routing for your web apps and microservices.
apo - A.P.O. - "Authorized Personnel Only" is a minimalist OAuth IAM written in Go
Express - Fast, unopinionated, minimalist web framework for node.