Echo VS go-kit

The little go book, Maybe that can help you a little bit, and then you could try echo High performance, extensible, minimalist Go web framework. 👌🏻 It has good documentation.

The project uses echo for serve as an http server, and we saved the config at the api/server.go file:

You should learn Echo and net http simultaneously, and I'll explain why. Go has a very high quality standard library which comes with a production quality web server and templating, and it has lightweight threads and concurrency primitives built into the language. So basically every library and framework builds on top of what is already there and as rule stuff integrates very well. I recommend Echo specifically because while there are lots of good frameworks, I think Echo is particularly good when it comes to documentation and code examples, i.e. beginner-friendly.

for me, Echo gives me that sense https://echo.labstack.com/

I'm thinking of recreating something like silverbullet using Vite, Svelte, Echo, Sqlite, anime, and web sockets. I'll host it in Docker on my mini server, access it via Tailscale and back it up with restic to Azure. I have some vague idea of building a web app that is both the editor and the app at the same time. Like a game where you build the game by playing the game, but with markdown and magic. Perfect side project fodder.

i prefer echo https://echo.labstack.com/ but from these two, i'd choose fiber

labstack/echo

Echo

I use https://echo.labstack.com/, it's minimalist. Pocketbase also uses Echo.

To implement service discovery in our GoLang microservice we will use GoKit, a toolkit for microservices that provides support to auth, log, service discovery, tracing and more. For this starter code the mod already installed, you can skip this step

My company uses go-kit

For reference my company Go projects are built with (go-kit)[https://gokit.io/] design patterns.

5. kit. The kit framework is a programming toolkit for building robust, reliable, and maintainable microservices in Golang. It is a collection of packages and best practices that offer businesses of all sizes a thorough, reliable, and trustworthy way to create microservices. Go is a fantastic general-purpose language, but microservices need some specialized assistance. As a result, the kit framework offers infrastructure integration, system observability, and Remote Procedure Call (RPC) safety. Golang is a first-class language for creating microservices in any organization thanks to its composition of numerous closely related packages that together form an opinionated framework for building substantial Service-Oriented Architectures (SOAs).It was created with interoperability in mind, and developers are free to select the platforms, databases, components, and architectural styles that best suit their needs. The disadvantage of using go-kit is that it has a high overhead for adding API to the service because of how heavily it relies on interfaces. Documentation Link: https://github.com/go-kit/kit

At first I was confused but this GitHub user/org is completely different from the massively popular go-kit/kit https://github.com/go-kit/kit

https://github.com/go-kit/kit#related-projects

go-micro seems like it does a bit too much, like service discovery and balancing within the framework when that's likely better handled by an Envoy/Istio.

see also: https://github.com/go-kit/kit

Or see also: https://medium.com/code-zen/why-i-don-t-use-go-web-framework... (or any of the dozens of blogs of people indicating why you dont need a framework for go)

I think the more interesting aspect of this is the framework being used: https://github.com/micro/micro

I haven't dug into it at all yet, but at a glance it looks like it's aiming to do something similar to what Go kit (https://gokit.io/) or Finagle (https://twitter.github.io/finagle/) does, where it gives you a nice abstraction for defining your "service" and then handles all the supplementary aspects (service discovery, serialization, retry/circuit breaker logic, rate limiting, hooks for logging, tracing, and metrics, etc) so you don't have to build those from scratch every time.

I don't know if any of those other frameworks could really be considered very "successful" outside the original organizations they were built for (it seems like the industry has bet more on service meshes and API gateway products), but I'd probably be more inclined to start with one of them than making a new framework.

I wish more people encouraged people new to Go to look at some of the targets you'll arrive at so that people don't come into Go thinking the end result is going to be using the Go version of Laravel, Spring, or Rails.

Go has some interesting ideas about models/ORM's, OpenAPI, validation, templates, embedded binary files and other things. When types mater, like in Go, code generation is often very important as well which isn't as common in scripting languages.

https://goa.design/ for grpc/rest servers based on specs

https://gokit.io/ for microservices

https://github.com/mustafaakin/gongular for object-based validation

https://sqlc.dev/ for generated models based on SQL (skip the whole idea of an ORM)

https://github.com/jmoiron/sqlx for more traditional object population from SQL

https://pkg.go.dev/errors for an understanding of wrapping errors and nested error causes

https://gqlgen.com/ for auto-generated revolvers based on GraphQL schemas

https://pkg.go.dev/io#Reader all the Reader/Writer/Closer's as they are everywhere since Go cares about performance and therefore streaming abilities. No more string passing.