Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Sandglass
Sandglass

1
4
+ 1
0
simplehttp
simplehttp

1
4
+ 1
0
Add tool

Sandglass vs simplehttp: What are the differences?

Developers describe Sandglass as "Distributed, scalable, persistent time-sorted message queue". A distributed, horizontally scalable, persistent, time ordered message queue. Developed to support asynchronous tasks and message scheduling which makes it suitable for usage as a task queue. On the other hand, simplehttp is detailed as "A family of libraries and daemons built upon libevent that make high performance HTTP servers simple and straightforward to write". .

Sandglass and simplehttp can be primarily classified as "Message Queue" tools.

Sandglass and simplehttp are both open source tools. Sandglass with 1.52K GitHub stars and 40 forks on GitHub appears to be more popular than simplehttp with 480 GitHub stars and 73 GitHub forks.

What is Sandglass?

A distributed, horizontally scalable, persistent, time ordered message queue. Developed to support asynchronous tasks and message scheduling which makes it suitable for usage as a task queue.

What is simplehttp?

Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Sandglass?
Why do developers choose simplehttp?
    Be the first to leave a pro
      Be the first to leave a pro
        Be the first to leave a con
          Be the first to leave a con
          What companies use Sandglass?
          What companies use simplehttp?
            No companies found

            Sign up to get full access to all the companiesMake informed product decisions

            What tools integrate with Sandglass?
            What tools integrate with simplehttp?
              No integrations found

              Sign up to get full access to all the tool integrationsMake informed product decisions

              What are some alternatives to Sandglass and simplehttp?
              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 is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
              Amazon SQS
              Transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. With SQS, you can offload the administrative burden of operating and scaling a highly available messaging cluster, while paying a low price for only what you use.
              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.
              ActiveMQ
              Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4. Apache ActiveMQ is released under the Apache 2.0 License.
              See all alternatives
              Decisions about Sandglass and simplehttp
              No stack decisions found
              Interest over time
              Reviews of Sandglass and simplehttp
              No reviews found
              How developers use Sandglass and simplehttp
              No items found
              How much does Sandglass cost?
              How much does simplehttp cost?
              Pricing unavailable
              Pricing unavailable
              News about Sandglass
              More news
              News about simplehttp
              More news