microservice1
By uberswe
notify
A microservice using Redis to enable a stateful multi-channel notification system (by go-bridget)
microservice1 | notify | |
---|---|---|
1 | 2 | |
- | 2 | |
- | - | |
- | 1.9 | |
- | 12 months ago | |
Go | ||
- | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
microservice1
Posts with mentions or reviews of microservice1.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-09-30.
-
Migrating from PHP to Go
For what you are trying to do with micro services I would recommend having a main service and just make your modules folders in that repo. Let's say I make a repo at github.com/uberswe/microservice1 then I might let microservice 2 import the database package defined in microservice1 using github.com/uberswe/microservice1/database
notify
Posts with mentions or reviews of notify.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-09-30.
-
Kafka as chat server?
Redis. The pub/sub is sufficient. Here's a notification service that plugs websockets in on one end: https://github.com/go-bridget/notify - I might add in server-side push support, or gobws to keep memory use down. A chat service can be implemented with a rpc API for write operations, and the notify websocket service to deliver events (new messages,...) and state (history, search,...).
-
Migrating from PHP to Go
I'm a big fan of [Twirp RPC](https://github.com/twitchtv/twirp), and [go-chi/chi](https://github.com/go-chi/chi) if I need to provide REST endpoints, authentication or other routing middleware. The "gorilla" set of packages are also useful, I always reach for gorilla/websocket if I need to do some websocket work. You can look at an example service in [go-bridget/notify](https://github.com/go-bridget/notify) - the main files to look at are under rpc/notify/notify.proto/.go, and the implementation which you write is under server/notify. If you'd create database drivers, I'd create a package under server/notify/mysql (for example), and then implement an interface for data retrieval/settings. It's on the todolist, if I'll ever need to implement anything other than JWT, or Redis. Comment if you have any questions or notes.
What are some alternatives?
When comparing microservice1 and notify you can also consider the following projects:
client_golang - Prometheus instrumentation library for Go applications
GORM - The fantastic ORM library for Golang, aims to be developer friendly
go-formatter - A curated list of awesome Go frameworks, libraries and software
goqu - SQL builder and query library for golang
mux - A powerful HTTP router and URL matcher for building Go web servers with 🦍