watermill VS Fiber

I’ve successfully worked on projects using an asynchronous event-driven way of connecting services. I really like the decoupling of business logic and the events triggering it. I highly recommend https://github.com/ThreeDotsLabs/watermill to be more flexible when it comes to choosing the actual technology driving the async patter. It might be NATS today but requirements might change and you need to change. Watermill prepares you for this.

Highly recommend https://watermill.io lib for building async apps (using among others pub/sub patterns). It greatly decouples your code from the underlying technology and gives you the freedom to choose depending on the environment (e.g dev, prod). For dev or small scale purposes, it supports pub/sub purely based on go channels.

Look at this library: https://github.com/ThreeDotsLabs/watermill

Watermill is a good pubsub abstraction. You can start with native go channels and grow into a cloud pubsub or Kafka/Pulsar if you need to.

These conditions have led me to discover two packages watermill.io and go-kit. Both of these seem to do what I want and I am thinking of implementing the project using watermill and go Chanels and deploying to a server or some sort.

github.com/ThreeDotsLabs/watermill package provides a framework for building event-driven applications. It allows easy communication between independent components by decoupling the sender and the receiver.

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

Checkout https://watermill.io/

To make my life easier, I added Fiber, a popular lightweight framework. Regardless of which package you use, the process and most of the code will remain unchanged.

Since you're from Nodejs just like me, I use fiber https://gofiber.io/ it's easier to understand from a Nodejs background (express, etc) and there's nothing wrong using it if you know it, your casual application wont need all the performance in the world Go provides

I think u should try Fiber it's the fastest according to the benchmarks and imo it's the best I love it!!!

Boneless is a powerful tool that offers a wide range of features to facilitate application development. In this blog post, we will explore some essential tools that can be used in conjunction with Boneless: Service Weaver, Go Migrate, SQLC, and Fiber. Let's discover how these tools can boost productivity and efficiency in application development.

Fiber

Fibber is web framework written in Go. It is very easy to learn. https://gofiber.io

don’t have an API at all - it’s a security vulnerability and unless you already know how to secure an API suite it’s very likely to increase risk for a dependent project. if you’re set on an API, use a well known routing package (e.g I love gofiber), and add an optional .withMiddleware() to your start func to allow clients to extend and secure the API themselves

I have loved using fiber. Very nice API with lots of configurability and it scales very well compared to echo, gin, etc.