Amazon Kinesis Firehose vs AWS Snowball Edge: What are the differences?
Amazon Kinesis Firehose: Simple and Scalable Data Ingestion. Amazon Kinesis Firehose is the easiest way to load streaming data into AWS. It can capture and automatically load streaming data into Amazon S3 and Amazon Redshift, enabling near real-time analytics with existing business intelligence tools and dashboards you’re already using today; AWS Snowball Edge: Petabyte-scale data transport with on-board storage and compute. AWS Snowball Edge is a 100TB data transfer device with on-board storage and compute capabilities. You can use Snowball Edge to move large amounts of data into and out of AWS, as a temporary storage tier for large local datasets, or to support local workloads in remote or offline locations.
Amazon Kinesis Firehose belongs to "Real-time Data Processing" category of the tech stack, while AWS Snowball Edge can be primarily classified under "Data Transfer".
What is Amazon Kinesis Firehose?
What is AWS Snowball Edge?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Amazon Kinesis Firehose?
Why do developers choose AWS Snowball Edge?
What are the cons of using Amazon Kinesis Firehose?
What are the cons of using AWS Snowball Edge?
What companies use AWS Snowball Edge?
Sign up to get full access to all the companiesMake informed product decisions
We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.
To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda 3. #Data - Amazon RDS , Amazon DynamoDB , Amazon S3 , MongoDB Atlas
To build #Webapps we decided to use Angular 2 with RxJS
#Devops - GitHub , Travis CI , Terraform , Docker , Serverless