cadence
nsq
Our great sponsors
cadence | nsq | |
---|---|---|
19 | 14 | |
7,771 | 24,516 | |
1.5% | 0.4% | |
9.7 | 6.3 | |
5 days ago | 12 days 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.
cadence
- Show HN: Hatchet – Open-source distributed task queue
-
Ask HN: Who is hiring? (December 2023)
Uber | Software Engineers | Hybrid (Denmark) | https://www.uber.com/dk/en/careers/locations/aarhus/
Work with an amazing team responsible for the infrastructure software that makes Uber’s data centers around the world reliable and scalable. If you want to solve the toughest engineering challenges alongside some of the smartest people in the industry, Uber Aarhus is the right place for you.
The team in Aarhus build and operate the stateless and stateful compute platforms used by nearly every other engineer in the company (Up - https://www.uber.com/en-GB/blog/up-portable-microservices-re... and Odin - https://www.uber.com/en-GB/blog/how-uber-optimized-cassandra...) as well as other related infrastructure projects such as Cadence - https://github.com/uber/cadence.
-
Best way to schedule events and handle them in the future?
May be this..https://cadenceworkflow.io/
- Mandala: experiment data management as a built-in (Python) language feature
-
Why messaging is much better than REST for inter-microservice communications
Having done a reasonable amount of messaging code in my time, I would say the final form of this sort of thing might look more like Cadence[0] than anything like this.
-
cadence VS javactrl-kafka - a user suggested alternative
2 projects | 2 Feb 2023
-
[P] My co-founder and I quit our engineering jobs at AWS to build “Tensor Search”. Here is why.
Emit events from your primary DB (postgres, etc.) to something like kafka or rabbitmq and then catch that in your search engine. There's also some end-to-end solutions like temporal (temporal.io) or cadence (https://cadenceworkflow.io/)
-
Workflow Engines
Are there any mature workflow engines such as https://github.com/uber/cadence but with Rust client support?
-
How can you ensure all Microservices have finished their tasks?
You should definitely check Uber Cadence https://cadenceworkflow.io/
- Apache Hop 2.0
nsq
-
MQTT vs. Kafka: An IoT Advocate's Perspective
Interesting. What are you thoughts on NSQ?
Was looking at it earlier today, but haven't ever tried it out.
-
Any thoughts on using Redis to extend Go's channels across application / machine boundaries?
(G)NATS can do millions of messages per second and is the right tool for the job (either that or NSQ). Redis isn't even the fastest Redis protocol implementation, KeyDB significantly outperforms it.
-
FileWave: Why we moved from ZeroMQ to NATS
Bit.ly's NSQ is also an excellent message queue option.
-
Infinite loop pattern to poll for a queue in a REST server app
Queue consumers are interesting because there are many solutions for them, from using Redis and persisting the data in a data store - but for fast and scalable the approach I would take is something like SQS (as I advocate AWS even free tier) or NSQ for managing your own distributed producers and consumers.
-
What are pros and cons of Go?
distrubition server engine ( for example websocket server multi ws gateway and worker pool,nsq.io realtime message queue and so on)
- Is there any conventionally accepted repo that is representative of well designed go code ?
-
Distributed IM Service in Golang
NSQ is a message queue implemented by Golang, and all messages are routed through NSQ. Reasons for choosing NSQ compared to other MQs: decentralized distribution (direct connection between production and consumption), low latency, No ordering, high performance, simple binary protocol.
-
Fluvio: The Programmable Data Platform
If we are talking about "cloud-native", I would really recommend taking a look at nsq or nats. I am really big fanboy of NSQ [1], it is simple, easy to setup and conceptually easy to learn.
[1] https://nsq.io
-
For those running Go in production at scale, what do you use for distributed task queues?
Here is link number 1 - Previous text "NSQ"
I've been using NSQ in production for a number of years now. It's also written in Go and has a first class client library maintained by the devs
What are some alternatives?
NATS - Golang client for NATS, the cloud native messaging system.
NATS - High-Performance server for NATS.io, the cloud and edge native messaging system.
temporal - Temporal service
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
Apache Kafka - Mirror of Apache Kafka
Flowable (V6) - A compact and highly efficient workflow and Business Process Management (BPM) platform for developers, system admins and business users.
ZeroMQ - ZeroMQ core engine in C++, implements ZMTP/3.1
etcd - Distributed reliable key-value store for the most critical data of a distributed system
consul - Consul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.
fluvio - Lean and mean distributed stream processing system written in rust and web assembly.
go-proxy-cache - Simple Reverse Proxy with Caching, written in Go, using Redis.
Asynq - Simple, reliable, and efficient distributed task queue in Go