Amazon SQS vs Oracle

Overview

Amazon SQS

Stacks2.8K

Followers2.0K

Votes171

Oracle

Stacks2.6K

Followers1.8K

Votes113

Amazon SQS vs Oracle: What are the differences?

Introduction:

In this article, we will discuss the key differences between Amazon Simple Queue Service (SQS) and Oracle. Both Amazon SQS and Oracle are cloud-based messaging services that offer reliable message queues for applications to communicate asynchronously. However, there are several important differences between them.

Pricing Model: One of the key differences between Amazon SQS and Oracle is the pricing model. Amazon SQS offers a pay-per-use pricing model, where you only pay for the number of messages and data transfer involved in your application. On the other hand, Oracle has a subscription-based pricing model, where you pay a fixed monthly fee regardless of the number of messages or data transfer.
Message Visibility: Another difference between Amazon SQS and Oracle is the message visibility feature. In Amazon SQS, once a message is retrieved by a consumer, it becomes invisible to other consumers until the visibility timeout period expires. This ensures that the message is processed by only one consumer. However, Oracle does not provide a built-in message visibility feature, and it is the responsibility of the consumers to implement this functionality.
Message Retention: Amazon SQS and Oracle also differ in their message retention policies. With Amazon SQS, messages can be retained in the queue for a maximum of 14 days, allowing consumers to retrieve and process them at their own pace. In contrast, Oracle has a shorter default retention period of 7 days in its messaging service.
Message Size Limit: Both Amazon SQS and Oracle impose limitations on the size of messages that can be sent through their messaging services. However, the maximum message size limit is significantly higher for Amazon SQS, which allows messages up to 256 KB in size. In contrast, Oracle has a smaller maximum message size limit of 64 KB.
Message Delivery Order: Amazon SQS guarantees the order of message delivery within a single message group. Messages that belong to different message groups can be delivered out of order. Oracle, on the other hand, provides in-order message delivery within the same partition key but does not guarantee the order across different partition keys.
Message Filtering: Amazon SQS offers a feature called message filtering, which allows consumers to retrieve only specific messages from a queue based on message attributes. This provides a flexible way of filtering messages and reduces the consumer's workload. Oracle, however, does not have built-in message filtering capabilities, and consumers need to implement their own filtering mechanisms.

In Summary, Amazon SQS and Oracle differ in their pricing models, message visibility, message retention policies, message size limits, message delivery order, and message filtering capabilities.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Amazon SQS, Oracle

Pulkit

Software Engineer

Oct 30, 2020

Needs adviceon

Django

Amazon SQS

RabbitMQ

Hi! I am creating a scraping system in Django, which involves long running tasks between 1 minute & 1 Day. As I am new to Message Brokers and Task Queues, I need advice on which architecture to use for my system. ( Amazon SQS, RabbitMQ, or Celery). The system should be autoscalable using Kubernetes(K8) based on the number of pending tasks in the queue.

474k views474k

Comments

Meili

Software engineer at Digital Science

Sep 24, 2020

Needs adviceon

ZeroMQ

RabbitMQ

Amazon SQS

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}|tool:1064| 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

500k views500k

Comments

MITHIRIDI

Software Engineer at LightMetrics

May 8, 2020

Needs adviceon

Amazon SQS

Amazon MQ

I want to schedule a message. Amazon SQS provides a delay of 15 minutes, but I want it in some hours.

Example: Let's say a Message1 is consumed by a consumer A but somehow it failed inside the consumer. I would want to put it in a queue and retry after 4hrs. Can I do this in Amazon MQ? I have seen in some Amazon MQ videos saying scheduling messages can be done. But, I'm not sure how.

303k views303k

Comments

Detailed Comparison

Amazon SQS	Oracle
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.	Oracle Database is an RDBMS. An RDBMS that implements object-oriented features such as user-defined types, inheritance, and polymorphism is called an object-relational database management system (ORDBMS). Oracle Database has extended the relational model to an object-relational model, making it possible to store complex business models in a relational database.
A queue can be created in any region.;The message payload can contain up to 256KB of text in any format. Each 64KB ‘chunk’ of payload is billed as 1 request. For example, a single API call with a 256KB payload will be billed as four requests.;Messages can be sent, received or deleted in batches of up to 10 messages or 256KB. Batches cost the same amount as single messages, meaning SQS can be even more cost effective for customers that use batching.;Long polling reduces extraneous polling to help you minimize cost while receiving new messages as quickly as possible. When your queue is empty, long-poll requests wait up to 20 seconds for the next message to arrive. Long poll requests cost the same amount as regular requests.;Messages can be retained in queues for up to 14 days.;Messages can be sent and read simultaneously.;Developers can get started with Amazon SQS by using only five APIs: CreateQueue, SendMessage, ReceiveMessage, ChangeMessageVisibility, and DeleteMessage. Additional APIs are available to provide advanced functionality.	-
Statistics
Stacks 2.8K	Stacks 2.6K
Followers 2.0K	Followers 1.8K
Votes 171	Votes 113
Pros & Cons
Pros 62 Easy to use, reliable 40 Low cost 28 Simple 14 Doesn't need to maintain it 8 It is Serverless Cons 2 Has a max message size (currently 256K) 2 Difficult to configure 2 Proprietary 1 Has a maximum 15 minutes of delayed messages only	Pros 44 Reliable 33 Enterprise 15 High Availability 5 Expensive 5 Hard to maintain Cons 14 Expensive

What are some alternatives to Amazon SQS, Oracle?

MongoDB

MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.

MySQL

The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.

PostgreSQL

PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.

Kafka

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

RabbitMQ

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

Microsoft SQL Server

Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.

SQLite

SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file.

Cassandra

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.

Memcached

Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.

MariaDB

Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry. MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.

Related Comparisons

Amazon SQS vs Oracle: What are the differences?

Introduction:

Pricing Model: One of the key differences between Amazon SQS and Oracle is the pricing model. Amazon SQS offers a pay-per-use pricing model, where you only pay for the number of messages and data transfer involved in your application. On the other hand, Oracle has a subscription-based pricing model, where you pay a fixed monthly fee regardless of the number of messages or data transfer.
Message Visibility: Another difference between Amazon SQS and Oracle is the message visibility feature. In Amazon SQS, once a message is retrieved by a consumer, it becomes invisible to other consumers until the visibility timeout period expires. This ensures that the message is processed by only one consumer. However, Oracle does not provide a built-in message visibility feature, and it is the responsibility of the consumers to implement this functionality.
Message Retention: Amazon SQS and Oracle also differ in their message retention policies. With Amazon SQS, messages can be retained in the queue for a maximum of 14 days, allowing consumers to retrieve and process them at their own pace. In contrast, Oracle has a shorter default retention period of 7 days in its messaging service.
Message Size Limit: Both Amazon SQS and Oracle impose limitations on the size of messages that can be sent through their messaging services. However, the maximum message size limit is significantly higher for Amazon SQS, which allows messages up to 256 KB in size. In contrast, Oracle has a smaller maximum message size limit of 64 KB.
Message Delivery Order: Amazon SQS guarantees the order of message delivery within a single message group. Messages that belong to different message groups can be delivered out of order. Oracle, on the other hand, provides in-order message delivery within the same partition key but does not guarantee the order across different partition keys.
Message Filtering: Amazon SQS offers a feature called message filtering, which allows consumers to retrieve only specific messages from a queue based on message attributes. This provides a flexible way of filtering messages and reduces the consumer's workload. Oracle, however, does not have built-in message filtering capabilities, and consumers need to implement their own filtering mechanisms.

In Summary, Amazon SQS and Oracle differ in their pricing models, message visibility, message retention policies, message size limits, message delivery order, and message filtering capabilities.

Amazon SQS vs Oracle

Overview