kago VS mux

The closest I’ve seen is https://github.com/kamalshkeir/kago it’s not only building the restful part but also the ORM using Go generics to match día go behavior. It even supports migrations

Feel free to join our discussions https://github.com/kamalshkeir/kago/discussions/7

exactly, chi is a very good router, but still not fit my use cases, so i make my own, that handle extra things i needed to have in my framework https://github.com/kamalshkeir/kago

i hate gin , donno echo very well, but i found that going from stdlib to build a small framework will give you very good experience, and the framework will be adapted to your need, feel free to check kago , a framework like django, very easy to get started with kago

Hello all, It may seem weird , but i will explain. KaGo is my new golang web framework, i deployed a website using it : kamalshkeir.dev , i tried my best to make this framework very secure, but i'm not an expert, that's why i think about this challenge for hacker gophers :p, to be able to find more vulnerabilities before people start using it. I give you all permissions to hack this website, so please feel free to tested like if it was you own website. Thank you all in advance

handle migration from struct , so detect when remove or add field to struct https://github.com/kamalshkeir/kago

https://github.com/kamalshkeir/kago , check the dependencies, you will see that everything is used, you can easily benchmark against gorm and against the standard library for example to compare performance , i have some benchmarks in the readme too

few days ago, i have maid a new portfolio/blog using my framework KaGo. I like to always run my small projects on vps and deploye them from scratch on ubuntu or centos, let's say to not forget my good practices. Long story short, i have never deployed an application using only the binary and systemd with a domain name and ssl, i have always used apache and nginx as proxy behind my app. Look at it now https://kamalshkeir.dev😁😁😁 , my gopher portdolio running listenandserveTLS with letsencrypt certificate, no proxy, no static files no templates , only the binary 9Mb running with systemd on the server. That's not all, my go app was using nothing from the power of my vps , less than 10% , so i said why i don't try grafana, prometheus, loki ..., all these good stuff. And that's why i'm so happy, i have finally the dashboard i have looking for, grafana dashboard , prometheus scraping all metrics from my go application, promtail and loki getting me the logs to the dashboard, node exporter showing me metrics for my linux system, and postgres exporter for my database, all in one place. i you want to look at it, you can 😁 , this is the link to grafana https://kamalshkeir.dev:9999 username: test password: testadmin

https://github.com/kamalshkeir/kago is pretty much like django, 2 min to get up and running

This is not a disproval, but gorilla/mux has comparatively poor benchmark results among popular (many stars) third-party HTTP routers. , used by many users.

This attention to detail also can mean that for key abstractions in a tool or framework, what concretely goes on doesn't go unexplained. For example, when I was learning Go for web development, my first stumbling block was understanding how interfaces worked, particularly http.Handler, which is key to doing web development with Go's powerful net/http package and the fits-like-a-glove package built on top of it, the Gorilla Mux router. My way of finding out how that worked, and seeing the elegance of that interface, was pretty unorthodox - I figured out how Handlers worked by looking directly at Go's source code (which also is a demonstration of Go's readability, if you're interested in joining the Gophers!). And coming out of that was my very first tech talk at in 2015, on learning Gorilla from its Node.js counterpart, Express.js!

In this ApiGateway implementation, we've employed the Gorilla Mux router for enhanced route handling. Let's break down the key components:

Now that we have set up the Go environment, we can start building our API. The first step is to choose a framework. There are several popular frameworks for building APIs in Go, such as Gorilla mux, Echo, and Gin. For this article, we'll use Gorilla mux.

Mir is a toolkit to develop RESTful API backend service like develop service of gRPC. It adapt some HTTP framework sush as Gin, Chi, Hertz, Echo, Iris, Fiber, Macaron, Mux, httprouter。

My personal favorite tools: - https://github.com/go-kit/ for building services (although it's not necessary a great tool for prototyping) - https://github.com/gorilla/mux router (although it's been recently deprecated, so I'm looking for a similar, maintained library) - https://entgo.io/ ORM - https://watermill.io/ for messaging

We will be using Gorilla Mux to create the APIs locally. Gorilla Mux implements a request router and dispatcher to match the incoming requests.