Alternatives to Gearman logo

Alternatives to Gearman

RabbitMQ, Kafka, Celery, Redis, and Beanstalkd are the most popular alternatives and competitors to Gearman.
76
144
+ 1
45

What is Gearman and what are its top alternatives?

Gearman is an open-source, distributed job scheduler that helps developers with parallel processing, backgrounding, and load balancing of tasks. It offers features such as multi-language support, real-time status updates, and scalability. However, its limitations include potential complexity in setup and configuration for beginners.

  1. Celery: Celery is a distributed task queue built on Python that supports scheduling, execution, and monitoring of tasks. It offers features like real-time monitoring, task retries, and priority settings. Pros include a large community and compatibility with various message brokers, while cons include potential complexity in setting up and maintaining.
  2. Apache Kafka: Apache Kafka is a distributed event streaming platform that can be used for data processing, messaging, and real-time analytics. Its key features include fault tolerance, high-throughput processing, and scalability. Pros of using Apache Kafka include high performance and fault tolerance, while cons may involve learning curve and infrastructure requirements.
  3. RabbitMQ: RabbitMQ is an open-source message broker software that supports multiple messaging protocols. It offers features like message queuing, routing, and clustering. Pros of RabbitMQ include high availability, clustering support, and a wide variety of plugins. However, potential cons include performance limitations and complexity in configuration.
  4. Resque: Resque is a Redis-backed job queue management tool built on Ruby that allows for background processing of tasks. Key features include retries, plugins, and monitoring. Pros of using Resque include simplicity, flexibility, and compatibility with Ruby on Rails applications. Cons may involve performance limitations at scale.
  5. AWS Lambda: AWS Lambda is a serverless compute service that allows developers to run code without provisioning or managing servers. It offers features like automatic scaling, event-driven architecture, and pay-per-use pricing. Pros of AWS Lambda include ease of use, scalability, and integration with other AWS services. Cons may include vendor lock-in and potential limitations in running long-lived tasks.
  6. Sidekiq: Sidekiq is a background job processing tool for Ruby, built on Redis. It provides features like job retries, dashboard for monitoring, and concurrency control. Pros of Sidekiq include speed, reliability, and ease of use. However, it may require familiarity with Redis and potential configuration overhead.
  7. IronMQ: IronMQ is a hosted message queue service that supports cloud-based messaging for any application or service. Its key features include push and pull queues, message durability, and monitoring. Pros of IronMQ include ease of setup, scalability, and reliability. Cons may involve cost considerations and dependency on a third-party service.
  8. Beanstalkd: Beanstalkd is a simple, fast work queue service that supports delaying, prioritizing, and organizing jobs. It offers features like job burying, real-time monitoring, and protocol support. Pros of Beanstalkd include speed, simplicity, and reliability. Cons may involve limited features compared to more robust solutions.
  9. Kubernetes Jobs: Kubernetes Jobs are a way to create and manage pods that run to completion in a Kubernetes cluster. Key features include parallelism, retries, and scaling. Pros of using Kubernetes Jobs include integration with Kubernetes ecosystem, scalability, and fault-tolerance. Cons may involve complexity in setup and management for beginners.
  10. Dask: Dask is a flexible parallel computing library for analytic computing in Python. It offers task scheduling, parallel execution, and integration with NumPy and Pandas. Pros of Dask include scalability, integration with existing Python libraries, and support for complex computations. Cons may involve learning curve and potential configuration overhead.

Top Alternatives to Gearman

  • RabbitMQ
    RabbitMQ

    RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received. ...

  • Kafka
    Kafka

    Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design. ...

  • Celery
    Celery

    Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well. ...

  • Redis
    Redis

    Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Redis provides data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes, and streams. ...

  • Beanstalkd
    Beanstalkd

    Beanstalks's interface is generic, but was originally designed for reducing the latency of page views in high-volume web applications by running time-consuming tasks asynchronously. ...

  • Laravel
    Laravel

    It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching. ...

  • ZeroMQ
    ZeroMQ

    The 0MQ lightweight messaging kernel is a library which extends the standard socket interfaces with features traditionally provided by specialised messaging middleware products. 0MQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more. ...

  • JavaScript
    JavaScript

    JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles. ...

Gearman alternatives & related posts

RabbitMQ logo

RabbitMQ

21.1K
18.5K
557
Open source multiprotocol messaging broker
21.1K
18.5K
+ 1
557
PROS OF RABBITMQ
  • 235
    It's fast and it works with good metrics/monitoring
  • 80
    Ease of configuration
  • 60
    I like the admin interface
  • 52
    Easy to set-up and start with
  • 22
    Durable
  • 19
    Standard protocols
  • 19
    Intuitive work through python
  • 11
    Written primarily in Erlang
  • 9
    Simply superb
  • 7
    Completeness of messaging patterns
  • 4
    Reliable
  • 4
    Scales to 1 million messages per second
  • 3
    Better than most traditional queue based message broker
  • 3
    Distributed
  • 3
    Supports MQTT
  • 3
    Supports AMQP
  • 2
    Clear documentation with different scripting language
  • 2
    Better routing system
  • 2
    Inubit Integration
  • 2
    Great ui
  • 2
    High performance
  • 2
    Reliability
  • 2
    Open-source
  • 2
    Runs on Open Telecom Platform
  • 2
    Clusterable
  • 2
    Delayed messages
  • 1
    Supports Streams
  • 1
    Supports STOMP
  • 1
    Supports JMS
CONS OF RABBITMQ
  • 9
    Too complicated cluster/HA config and management
  • 6
    Needs Erlang runtime. Need ops good with Erlang runtime
  • 5
    Configuration must be done first, not by your code
  • 4
    Slow

related RabbitMQ posts

James Cunningham
Operations Engineer at Sentry · | 18 upvotes · 1.7M views
Shared insights
on
CeleryCeleryRabbitMQRabbitMQ
at

As Sentry runs throughout the day, there are about 50 different offline tasks that we execute—anything from “process this event, pretty please” to “send all of these cool people some emails.” There are some that we execute once a day and some that execute thousands per second.

Managing this variety requires a reliably high-throughput message-passing technology. We use Celery's RabbitMQ implementation, and we stumbled upon a great feature called Federation that allows us to partition our task queue across any number of RabbitMQ servers and gives us the confidence that, if any single server gets backlogged, others will pitch in and distribute some of the backlogged tasks to their consumers.

#MessageQueue

See more

Around the time of their Series A, Pinterest’s stack included Python and Django, with Tornado and Node.js as web servers. Memcached / Membase and Redis handled caching, with RabbitMQ handling queueing. Nginx, HAproxy and Varnish managed static-delivery and load-balancing, with persistent data storage handled by MySQL.

See more
Kafka logo

Kafka

23.3K
21.8K
607
Distributed, fault tolerant, high throughput pub-sub messaging system
23.3K
21.8K
+ 1
607
PROS OF KAFKA
  • 126
    High-throughput
  • 119
    Distributed
  • 92
    Scalable
  • 86
    High-Performance
  • 66
    Durable
  • 38
    Publish-Subscribe
  • 19
    Simple-to-use
  • 18
    Open source
  • 12
    Written in Scala and java. Runs on JVM
  • 9
    Message broker + Streaming system
  • 4
    KSQL
  • 4
    Avro schema integration
  • 4
    Robust
  • 3
    Suport Multiple clients
  • 2
    Extremely good parallelism constructs
  • 2
    Partioned, replayable log
  • 1
    Simple publisher / multi-subscriber model
  • 1
    Fun
  • 1
    Flexible
CONS OF KAFKA
  • 32
    Non-Java clients are second-class citizens
  • 29
    Needs Zookeeper
  • 9
    Operational difficulties
  • 5
    Terrible Packaging

related Kafka posts

Nick Rockwell
SVP, Engineering at Fastly · | 46 upvotes · 3.6M views

When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

See more
Ashish Singh
Tech Lead, Big Data Platform at Pinterest · | 38 upvotes · 3M views

To provide employees with the critical need of interactive querying, we’ve worked with Presto, an open-source distributed SQL query engine, over the years. Operating Presto at Pinterest’s scale has involved resolving quite a few challenges like, supporting deeply nested and huge thrift schemas, slow/ bad worker detection and remediation, auto-scaling cluster, graceful cluster shutdown and impersonation support for ldap authenticator.

Our infrastructure is built on top of Amazon EC2 and we leverage Amazon S3 for storing our data. This separates compute and storage layers, and allows multiple compute clusters to share the S3 data.

We have hundreds of petabytes of data and tens of thousands of Apache Hive tables. Our Presto clusters are comprised of a fleet of 450 r4.8xl EC2 instances. Presto clusters together have over 100 TBs of memory and 14K vcpu cores. Within Pinterest, we have close to more than 1,000 monthly active users (out of total 1,600+ Pinterest employees) using Presto, who run about 400K queries on these clusters per month.

Each query submitted to Presto cluster is logged to a Kafka topic via Singer. Singer is a logging agent built at Pinterest and we talked about it in a previous post. Each query is logged when it is submitted and when it finishes. When a Presto cluster crashes, we will have query submitted events without corresponding query finished events. These events enable us to capture the effect of cluster crashes over time.

Each Presto cluster at Pinterest has workers on a mix of dedicated AWS EC2 instances and Kubernetes pods. Kubernetes platform provides us with the capability to add and remove workers from a Presto cluster very quickly. The best-case latency on bringing up a new worker on Kubernetes is less than a minute. However, when the Kubernetes cluster itself is out of resources and needs to scale up, it can take up to ten minutes. Some other advantages of deploying on Kubernetes platform is that our Presto deployment becomes agnostic of cloud vendor, instance types, OS, etc.

#BigData #AWS #DataScience #DataEngineering

See more
Celery logo

Celery

1.6K
1.6K
280
Distributed task queue
1.6K
1.6K
+ 1
280
PROS OF CELERY
  • 99
    Task queue
  • 63
    Python integration
  • 40
    Django integration
  • 30
    Scheduled Task
  • 19
    Publish/subsribe
  • 8
    Various backend broker
  • 6
    Easy to use
  • 5
    Great community
  • 5
    Workflow
  • 4
    Free
  • 1
    Dynamic
CONS OF CELERY
  • 4
    Sometimes loses tasks
  • 1
    Depends on broker

related Celery posts

James Cunningham
Operations Engineer at Sentry · | 21 upvotes · 358.1K views

Sentry started as (and remains) an open-source project, growing out of an error logging tool built in 2008. That original build nine years ago was Django and Celery (Python’s asynchronous task codebase), with PostgreSQL as the database and Redis as the power behind Celery.

We displayed a truly shrewd notion of branding even then, giving the project a catchy name that companies the world over remain jealous of to this day: django-db-log. For the longest time, Sentry’s subtitle on GitHub was “A simple Django app, built with love.” A slightly more accurate description probably would have included Starcraft and Soylent alongside love; regardless, this captured what Sentry was all about.

#MessageQueue #InMemoryDatabases

See more
James Cunningham
Operations Engineer at Sentry · | 18 upvotes · 1.7M views
Shared insights
on
CeleryCeleryRabbitMQRabbitMQ
at

As Sentry runs throughout the day, there are about 50 different offline tasks that we execute—anything from “process this event, pretty please” to “send all of these cool people some emails.” There are some that we execute once a day and some that execute thousands per second.

Managing this variety requires a reliably high-throughput message-passing technology. We use Celery's RabbitMQ implementation, and we stumbled upon a great feature called Federation that allows us to partition our task queue across any number of RabbitMQ servers and gives us the confidence that, if any single server gets backlogged, others will pitch in and distribute some of the backlogged tasks to their consumers.

#MessageQueue

See more
Redis logo

Redis

58.8K
45.2K
3.9K
Open source (BSD licensed), in-memory data structure store
58.8K
45.2K
+ 1
3.9K
PROS OF REDIS
  • 886
    Performance
  • 542
    Super fast
  • 513
    Ease of use
  • 444
    In-memory cache
  • 324
    Advanced key-value cache
  • 194
    Open source
  • 182
    Easy to deploy
  • 164
    Stable
  • 155
    Free
  • 121
    Fast
  • 42
    High-Performance
  • 40
    High Availability
  • 35
    Data Structures
  • 32
    Very Scalable
  • 24
    Replication
  • 22
    Great community
  • 22
    Pub/Sub
  • 19
    "NoSQL" key-value data store
  • 16
    Hashes
  • 13
    Sets
  • 11
    Sorted Sets
  • 10
    NoSQL
  • 10
    Lists
  • 9
    Async replication
  • 9
    BSD licensed
  • 8
    Bitmaps
  • 8
    Integrates super easy with Sidekiq for Rails background
  • 7
    Keys with a limited time-to-live
  • 7
    Open Source
  • 6
    Lua scripting
  • 6
    Strings
  • 5
    Awesomeness for Free
  • 5
    Hyperloglogs
  • 4
    Transactions
  • 4
    Outstanding performance
  • 4
    Runs server side LUA
  • 4
    LRU eviction of keys
  • 4
    Feature Rich
  • 4
    Written in ANSI C
  • 4
    Networked
  • 3
    Data structure server
  • 3
    Performance & ease of use
  • 2
    Dont save data if no subscribers are found
  • 2
    Automatic failover
  • 2
    Easy to use
  • 2
    Temporarily kept on disk
  • 2
    Scalable
  • 2
    Existing Laravel Integration
  • 2
    Channels concept
  • 2
    Object [key/value] size each 500 MB
  • 2
    Simple
CONS OF REDIS
  • 15
    Cannot query objects directly
  • 3
    No secondary indexes for non-numeric data types
  • 1
    No WAL

related Redis posts

Russel Werner
Lead Engineer at StackShare · | 32 upvotes · 2.6M views

StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

#StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 10M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
Beanstalkd logo

Beanstalkd

111
161
74
A simple, fast work queue
111
161
+ 1
74
PROS OF BEANSTALKD
  • 23
    Fast
  • 12
    Free
  • 12
    Does one thing well
  • 9
    Scalability
  • 8
    Simplicity
  • 3
    External admin UI developer friendly
  • 3
    Job delay
  • 2
    Job prioritization
  • 2
    External admin UI
CONS OF BEANSTALKD
    Be the first to leave a con

    related Beanstalkd posts

    Frédéric MARAND
    Core Developer at OSInet · | 2 upvotes · 233.1K views

    I used Kafka originally because it was mandated as part of the top-level IT requirements at a Fortune 500 client. What I found was that it was orders of magnitude more complex ...and powerful than my daily Beanstalkd , and far more flexible, resilient, and manageable than RabbitMQ.

    So for any case where utmost flexibility and resilience are part of the deal, I would use Kafka again. But due to the complexities involved, for any time where this level of scalability is not required, I would probably just use Beanstalkd for its simplicity.

    I tend to find RabbitMQ to be in an uncomfortable middle place between these two extremities.

    See more
    Laravel logo

    Laravel

    27.7K
    23K
    3.9K
    A PHP Framework For Web Artisans
    27.7K
    23K
    + 1
    3.9K
    PROS OF LARAVEL
    • 553
      Clean architecture
    • 392
      Growing community
    • 370
      Composer friendly
    • 344
      Open source
    • 324
      The only framework to consider for php
    • 220
      Mvc
    • 210
      Quickly develop
    • 168
      Dependency injection
    • 156
      Application architecture
    • 143
      Embraces good community packages
    • 73
      Write less, do more
    • 71
      Orm (eloquent)
    • 66
      Restful routing
    • 57
      Database migrations & seeds
    • 55
      Artisan scaffolding and migrations
    • 41
      Great documentation
    • 40
      Awesome
    • 30
      Awsome, Powerfull, Fast and Rapid
    • 29
      Build Apps faster, easier and better
    • 28
      Eloquent ORM
    • 26
      Promotes elegant coding
    • 26
      JSON friendly
    • 26
      Modern PHP
    • 25
      Most easy for me
    • 24
      Easy to learn, scalability
    • 23
      Beautiful
    • 22
      Blade Template
    • 21
      Test-Driven
    • 15
      Security
    • 15
      Based on SOLID
    • 13
      Cool
    • 13
      Clean Documentation
    • 13
      Easy to attach Middleware
    • 12
      Simple
    • 12
      Convention over Configuration
    • 11
      Easy Request Validatin
    • 10
      Simpler
    • 10
      Easy to use
    • 10
      Fast
    • 9
      Get going quickly straight out of the box. BYOKDM
    • 9
      Its just wow
    • 8
      Laravel + Cassandra = Killer Framework
    • 8
      Simplistic , easy and faster
    • 8
      Friendly API
    • 7
      Less dependencies
    • 7
      Super easy and powerful
    • 6
      Great customer support
    • 6
      Its beautiful to code in
    • 5
      Speed
    • 5
      Eloquent
    • 5
      Composer
    • 5
      Minimum system requirements
    • 5
      Laravel Mix
    • 5
      Easy
    • 5
      The only "cons" is wrong! No static method just Facades
    • 5
      Fast and Clarify framework
    • 5
      Active Record
    • 5
      Php7
    • 4
      Ease of use
    • 4
      Laragon
    • 4
      Laravel casher
    • 4
      Easy views handling and great ORM
    • 4
      Laravel Forge and Envoy
    • 4
      Cashier with Braintree and Stripe
    • 3
      Laravel Passport
    • 3
      Laravel Spark
    • 3
      Intuitive usage
    • 3
      Laravel Horizon and Telescope
    • 3
      Laravel Nova
    • 3
      Rapid development
    • 2
      Laravel Vite
    • 2
      Scout
    • 2
      Deployment
    • 1
      Succint sintax
    CONS OF LARAVEL
    • 54
      PHP
    • 33
      Too many dependency
    • 23
      Slower than the other two
    • 17
      A lot of static method calls for convenience
    • 15
      Too many include
    • 13
      Heavy
    • 9
      Bloated
    • 8
      Laravel
    • 7
      Confusing
    • 5
      Too underrated
    • 4
      Not fast with MongoDB
    • 1
      Slow and too much big
    • 1
      Not using SOLID principles
    • 1
      Difficult to learn

    related Laravel posts

    I need to build a web application plus android and IOS apps for an enterprise, like an e-commerce portal. It will have intensive use of MySQL to display thousands (40-50k) of live product information in an interactive table (searchable, filterable), live delivery tracking. It has to be secure, as it will handle information on customers, sales, inventory. Here is the technology stack: Backend: Laravel 7 Frondend: Vue.js, React or AngularJS?

    Need help deciding technology stack. Thanks.

    See more
    Christopher Wray
    Web Developer at Soltech LLC · | 15 upvotes · 175.6K views

    This week, we finally released NurseryPeople.com. In the end, I chose to provision our server on DigitalOcean. So far, I am SO happy with that decision. Although setting everything up was a challenge, and I learned a lot, DigitalOceans blogs helped in so many ways. I was able to set up nginx and the Laravel web app pretty smoothly. I am also using Buddy for deploying changes made in git, which is super awesome. All I have to do in order to deploy is push my code to my private repo, and buddy transfers everything over to DigitalOcean. So far, we haven't had any downtime and DigitalOceans prices are quite fair for the power under the hood.

    See more
    ZeroMQ logo

    ZeroMQ

    260
    584
    71
    Fast, lightweight messaging library that allows you to design complex communication system without much effort
    260
    584
    + 1
    71
    PROS OF ZEROMQ
    • 23
      Fast
    • 20
      Lightweight
    • 11
      Transport agnostic
    • 7
      No broker required
    • 4
      Low level APIs are in C
    • 4
      Low latency
    • 1
      Open source
    • 1
      Publish-Subscribe
    CONS OF ZEROMQ
    • 5
      No message durability
    • 3
      Not a very reliable system - message delivery wise
    • 1
      M x N problem with M producers and N consumers

    related ZeroMQ posts

    Shared insights
    on
    MongoDBMongoDBZeroMQZeroMQSpring BootSpring Boot

    In our Spring Boot application, which encompasses various projects, we employ ZeroMQ (ZMQ) for communication via a req/resp pattern. Recently, I observed that data is persisted in the MongoDB database before being transmitted to other applications. I've identified a method to monitor changes to the database, and I'm contemplating whether to utilize this monitoring approach to detect changes and execute the necessary instructions.

    Which approach is more advisable in this scenario: leveraging the database monitoring mechanism or sticking with the current ZMQ req/resp communication?

    Essentially, I'm seeking guidance on whether to rely on database monitoring for change detection and subsequent actions or to continue with the existing ZMQ communication pattern.

    See more
    Meili Triantafyllidi
    Software engineer at Digital Science · | 6 upvotes · 451K views
    Shared insights
    on
    Amazon SQSAmazon SQSRabbitMQRabbitMQZeroMQZeroMQ

    Hi, we are in a ZMQ set up in a push/pull pattern, and we currently start to have more traffic and cases that the service is unavailable or stuck. We want to: * Not loose messages in services outages * Safely restart service without losing messages (ZeroMQ seems to need to close the socket in the receiver before restart manually)

    Do you have experience with this setup with ZeroMQ? Would you suggest RabbitMQ or Amazon SQS (we are in AWS setup) instead? Something else?

    Thank you for your time

    See more
    JavaScript logo

    JavaScript

    354.7K
    269.7K
    8.1K
    Lightweight, interpreted, object-oriented language with first-class functions
    354.7K
    269.7K
    + 1
    8.1K
    PROS OF JAVASCRIPT
    • 1.7K
      Can be used on frontend/backend
    • 1.5K
      It's everywhere
    • 1.2K
      Lots of great frameworks
    • 897
      Fast
    • 745
      Light weight
    • 425
      Flexible
    • 392
      You can't get a device today that doesn't run js
    • 286
      Non-blocking i/o
    • 237
      Ubiquitousness
    • 191
      Expressive
    • 55
      Extended functionality to web pages
    • 49
      Relatively easy language
    • 46
      Executed on the client side
    • 30
      Relatively fast to the end user
    • 25
      Pure Javascript
    • 21
      Functional programming
    • 15
      Async
    • 13
      Full-stack
    • 12
      Setup is easy
    • 12
      Future Language of The Web
    • 12
      Its everywhere
    • 11
      Because I love functions
    • 11
      JavaScript is the New PHP
    • 10
      Like it or not, JS is part of the web standard
    • 9
      Everyone use it
    • 9
      Expansive community
    • 9
      Easy
    • 9
      Can be used in backend, frontend and DB
    • 8
      Easy to hire developers
    • 8
      No need to use PHP
    • 8
      For the good parts
    • 8
      Can be used both as frontend and backend as well
    • 8
      Powerful
    • 8
      Most Popular Language in the World
    • 7
      Evolution of C
    • 7
      Hard not to use
    • 7
      Versitile
    • 7
      Its fun and fast
    • 7
      Supports lambdas and closures
    • 7
      Love-hate relationship
    • 7
      Photoshop has 3 JS runtimes built in
    • 7
      Nice
    • 7
      It's fun
    • 7
      Popularized Class-Less Architecture & Lambdas
    • 7
      Agile, packages simple to use
    • 6
      Can be used on frontend/backend/Mobile/create PRO Ui
    • 6
      1.6K Can be used on frontend/backend
    • 6
      Client side JS uses the visitors CPU to save Server Res
    • 6
      It let's me use Babel & Typescript
    • 6
      Easy to make something
    • 5
      Client processing
    • 5
      Everywhere
    • 5
      Scope manipulation
    • 5
      Function expressions are useful for callbacks
    • 5
      Stockholm Syndrome
    • 5
      Promise relationship
    • 5
      Clojurescript
    • 5
      What to add
    • 4
      Only Programming language on browser
    • 4
      Because it is so simple and lightweight
    • 1
      Easy to understand
    • 1
      Test
    • 1
      Test2
    • 1
      Subskill #4
    • 1
      Easy to learn
    • 1
      Hard to learn
    • 1
      Not the best
    • 0
      Hard 彤
    CONS OF JAVASCRIPT
    • 22
      A constant moving target, too much churn
    • 20
      Horribly inconsistent
    • 15
      Javascript is the New PHP
    • 9
      No ability to monitor memory utilitization
    • 8
      Shows Zero output in case of ANY error
    • 7
      Thinks strange results are better than errors
    • 6
      Can be ugly
    • 3
      No GitHub
    • 2
      Slow
    • 0
      HORRIBLE DOCUMENTS, faulty code, repo has bugs

    related JavaScript posts

    Zach Holman

    Oof. I have truly hated JavaScript for a long time. Like, for over twenty years now. Like, since the Clinton administration. It's always been a nightmare to deal with all of the aspects of that silly language.

    But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.

    But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.

    Obviously there's a lot of things happening here, so just saying "JavaScript isn't terrible" might encompass a huge amount of libraries and frameworks. But if you're like me, yeah, give things another shot- I'm somehow not hating on JavaScript anymore and... gulp... I kinda love it.

    See more
    Conor Myhrvold
    Tech Brand Mgr, Office of CTO at Uber · | 44 upvotes · 11.3M views

    How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

    Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

    Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

    https://eng.uber.com/distributed-tracing/

    (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

    Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

    See more