Archive

The Dulin Report

Browsable archive from the WordPress export.

Results (43)

Strategic activity mapping for software architects May 25, 2025 The future is bright Mar 30, 2025 Comparing AWS SQS, SNS, and Kinesis: A Technical Breakdown for Enterprise Developers Feb 11, 2023 Should today’s developers worry about AI code generators taking their jobs? Dec 11, 2022 Scripting languages are tools for tying APIs together, not building complex systems Jun 8, 2022 Java is no longer relevant May 29, 2022 Best practices for building a microservice architecture Apr 25, 2022 TypeScript is a productivity problem in and of itself Apr 20, 2022 In most cases, there is no need for NoSQL Apr 18, 2022 A year of COVID taught us all how to work remotely Feb 10, 2021 What programming language to use for a brand new project? Feb 18, 2020 Microsoft acquires Citus Data Jan 26, 2019 The religion of JavaScript Nov 26, 2018 Teleportation can corrupt your data Sep 29, 2018 Let’s talk cloud neutrality Sep 17, 2018 What does a Chief Software Architect do? Jun 23, 2018 TypeScript starts where JavaScript leaves off Aug 2, 2017 Node.js is a perfect enterprise application platform Jul 30, 2017 Design patterns in TypeScript: Chain of Responsibility Jul 22, 2017 Rather than innovating Walmart bullies their tech vendors to leave AWS Jun 27, 2017 TDWI 2017, Chicago, IL: Architecting Modern Big Data API Ecosystems May 30, 2017 Copyright in the 21st century or how "IT Gurus of Atlanta" plagiarized my and other's articles Mar 21, 2017 Online grocers have an additional burden to be reliable Jan 5, 2017 Don't trust your cloud service until you've read the terms Sep 27, 2016 In search for the mythical neutrality among top-tier public cloud providers Jun 18, 2016 What can we learn from the last week's salesforce.com outage ? May 15, 2016 JEE in the cloud era: building application servers Apr 22, 2016 Managed IT is not the future of the cloud Apr 9, 2016 JavaScript as the language of the cloud Feb 20, 2016 Our civilization has a single point of failure Dec 16, 2015 IT departments must transform in the face of the cloud revolution Nov 9, 2015 We Live in a Mobile Device Notification Hell Aug 22, 2015 What Every College Computer Science Freshman Should Know Aug 14, 2015 Book Review: "Shop Class As Soulcraft" By Matthew B. Crawford Jul 5, 2015 Attracting STEM Graduates to Traditional Enterprise IT Jul 4, 2015 Your IT Department's Kodak Moment Jun 17, 2015 Big Data is not all about Hadoop May 30, 2015 Smart IT Departments Own Their Business API and Take Ownership of Data Governance May 13, 2015 What can Evernote Teach Us About Enterprise App Architecture Apr 2, 2015 Microsoft and Apple Have Everything to Lose if Chromebooks Succeed Mar 31, 2015 On apprenticeship Feb 13, 2015 Wall St. wakes up to underinvestment in OMS Aug 21, 2014 Cassandra: Lessons Learned Jun 6, 2014

Comparing AWS SQS, SNS, and Kinesis: A Technical Breakdown for Enterprise Developers

February 11, 2023

Queuing is a critical component of software architecture, and choosing the right system for your cloud-native enterprise application is crucial. In this blog post, we'll compare Amazon Simple Queue Service(SQS), Amazon Simple Notification Service (SNS), and Amazon Kinesis, exploring their strengths and weaknesses to help you determine which queuing system is best suited for your use case. 




Some background




Queuing is a fundamental aspect of software architecture that enables applications to manage incoming requests and prioritize tasks. It acts as a buffer between the application and its clients, allowing the application to process requests in an orderly and efficient manner. Queues can significantly improve performance, reliability, and scalability, especially in high-traffic or resource-intensive environments.



There are several types of queuing systems, including message queues, task queues, and event-driven queues. Message queues allow applications to exchange messages with each other, while task queues prioritize and manage long-running tasks. Event-driven queues allow applications to react to events in real time. Each type of queuing system has its use cases and benefits, and choosing the right one for your application depends on your specific requirements. Understanding the importance of queuing and its different types is essential for building a robust and scalable software architecture.




Amazon SQS




Amazon Simple Queue Service (SQS) is a highly scalable, fully managed message queuing service offered by AWS. It provides a distributed message queue for decoupling the components of a cloud-native enterprise application. With SQS, you can send, store, and receive messages between services, enabling asynchronous communication and helping to ensure that your application remains highly available and responsive.



SQS offers several key features, including support for standard and FIFO queues, the ability to send and receive an unlimited number of messages, and automatic scaling to handle changes in traffic. It also guarantees durability, ensuring that messages are stored redundantly across multiple availability zones. SQS can help you build scalable, reliable, and cost-effective cloud-native enterprise applications with these features. 




Amazon SNS




Amazon Simple Notification Service (SNS) is a flexible publish-subscribe messaging service offered by AWS. SNS enables you to send messages to multiple subscribers, including other AWS services, HTTP/S endpoints, email addresses, and mobile devices, allowing you to build applications that react to events in real time. SNS is often used in conjunction with other AWS services to build event-driven architectures, where components of an application can respond to changes in the environment in real time.



SNS offers support for multiple message formats, the ability to publish messages to multiple subscribers, and automatic retries in the event of delivery failures. It also guarantees durability, ensuring that messages are stored redundantly across multiple availability zones. SNS is an ideal solution for building highly scalable, reliable, and cost-effective cloud-native enterprise applications that require real-time event-driven processing. 




Amazon Kinesis




Kinesis allows you to collect, process, and analyze real-time data streams from multiple sources, including IoT devices, mobile apps, website clickstreams, and logs. Kinesis provides a real-time data processing platform that enables you to process and analyze large amounts of data in real time, making it an ideal solution for building real-time data-driven applications.



Kinesis supports real-time data processing, automatic scaling to handle changes in traffic, and the ability to handle millions of events per second. It also guarantees durability, ensuring data is stored redundantly across multiple availability zones. Kinesis is an ideal solution for building highly scalable, reliable, and cost-effective cloud-native enterprise applications that require real-time data processing and analysis. 




Side-by-side comparison of SQS, SNS and Kinesis: top 10





SQSSNSKinesis
PurposeA message queue service for decoupling components of an applicationA publish-subscribe messaging service for real-time event-driven processingA data streaming service for real-time data processing and analysis
Maximum message size256 KB256 KB for SMS, 2 KB for all others1 MB
Delivery guaranteeAt least onceBest effortOrdered, real-time
OrderingFIFO (best effort for standard)No guaranteeFIFO
Visibility timeoutUp to 12 hoursNoneNone
RetriesAutomated retries, configurableAutomated retriesNo retries, requires coding
SubscribersOne subscriberMultiple subscriberOne subscriber
Data retentionUp to 14 daysNoneUp to 24 hours, configurable up to 1 year
Realtime processingAsynchronousRealtimeRealtime
CostCheap for most use caseExpensive for high frequency useCan get expensive when processing large amounts of data




Integration and interoperability




Integration and interoperability are important considerations when choosing a queuing system for your cloud-native enterprise application. Integrating with other AWS services and external systems can significantly enhance the functionality and efficiency of your application. It is essential to carefully evaluate your requirements and consider the available options for integrating and interoperating with other systems.



Amazon Simple Queue Service (SQS), Amazon Simple Notification Service (SNS), and Amazon Kinesis can all be integrated with other AWS services and external systems. For example, SQS can be integrated with Amazon Lambda to trigger serverless functions in response to messages in a queue. SNS can be integrated with Amazon SES to send email notifications, and Kinesis can be integrated with Amazon Redshift for real-time data analysis. These integrations can be accomplished using the AWS Management Console, APIs, and SDKs. Additionally, all three services can be integrated with external systems using the HTTP/S protocol, enabling you to build complex, multi-tier architectures that span multiple cloud and on-premises environments.




Some final thoughts




In conclusion, choosing the right queuing system for your cloud-native enterprise application can significantly enhance your application's functionality, reliability, and performance. Amazon Simple Queue Service (SQS), Amazon Simple Notification Service (SNS), and Amazon Kinesis are all highly scalable, fully managed, and flexible queuing systems offered by AWS. SQS is a message queue service for decoupling components of an application, SNS is a publish-subscribe messaging service for real-time event-driven processing, and Kinesis is a data streaming service for real-time data processing and analysis. When deciding which queuing system to use, it is important to carefully evaluate your requirements, consider the available options for integration and interoperability, and choose the solution that best fits your needs.