ActiveMQ vs Cassandra: What are the differences?
What is ActiveMQ? A message broker written in Java together with a full JMS client. 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.
What is Cassandra? A partitioned row store. Rows are organized into tables with a required primary key. Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.
ActiveMQ belongs to "Message Queue" category of the tech stack, while Cassandra can be primarily classified under "Databases".
"Open source" is the top reason why over 9 developers like ActiveMQ, while over 96 developers mention "Distributed" as the leading cause for choosing Cassandra.
ActiveMQ and Cassandra are both open source tools. Cassandra with 5.23K GitHub stars and 2.33K forks on GitHub appears to be more popular than ActiveMQ with 1.49K GitHub stars and 1.04K GitHub forks.
According to the StackShare community, Cassandra has a broader approval, being mentioned in 337 company stacks & 231 developers stacks; compared to ActiveMQ, which is listed in 33 company stacks and 17 developer stacks.
What is ActiveMQ?
What is Cassandra?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using ActiveMQ?
What are the cons of using Cassandra?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Stitch is a wrapper around a Cassandra database. It has a web application that provides read-access to the counts through an HTTP API. The counts are written to Cassandra in two distinct ways, and it's possible to use either or both of them:
Real-time: For real-time updates, Stitch has a processor application that handles a stream of events coming from a broker and increments the appropriate counts in Cassandra.
Batch: The batch part is a MapReduce job running on Hadoop that reads event logs, calculates the overall totals, and bulk loads this into Cassandra.
Cassandra is our data management workhorse. It handles all our key-value services, supports time-series data storage and retrieval, securely stores all our audit trails, and backs our Datomic database.
While we experimented with Cassandra in the past, we are no longer using it. It is, however, open for consideration in future projects.
We are using Cassandra in a few of our apps. One of them is as a count service application to track the number of shares, clicks.. etc
Remote broker and local client for incoming data feeds. Local broker for republishing data feeds to other systems.