Amazon RDS for Aurora vs TempoDB: What are the differences?
Developers describe Amazon RDS for Aurora as "MySQL and PostgreSQL compatible relational database with several times better performance". Amazon Aurora is a MySQL-compatible, relational database engine that combines the speed and availability of high-end commercial databases with the simplicity and cost-effectiveness of open source databases. Amazon Aurora provides up to five times better performance than MySQL at a price point one tenth that of a commercial database while delivering similar performance and availability. On the other hand, TempoDB is detailed as "Store & analyze time series data from sensors, smart meters, servers & more". TempoDB is the first database service for time series data (ex: measuring thermostat temperatures, network latencies, heart rates). Time series is a unique Big Data problem that breaks traditional databases (MySQL, MongoDB, etc). Today, businesses spend months and millions attempting to build solutions to manage all this data and yet still fail to store as much as they need or analyze it effectively. TempoDB is a purpose-built database service that enables businesses to store and analyze massive streams of time series data, so they can learn from the past, understand the present, and predict the future.
Amazon RDS for Aurora and TempoDB belong to "SQL Database as a Service" category of the tech stack.
Some of the features offered by Amazon RDS for Aurora are:
- High Throughput with Low Jitter
- Push-button Compute Scaling
- Storage Auto-scaling
On the other hand, TempoDB provides the following key features:
- Flexible, powerful API
- Store as much high resolution (1 ms max) time series data as you need for long range historical analysis
- We guarantee data availability and protect against loss by replicating each live datapoint 3x and using geographically distributed backup environments
What is Amazon RDS for Aurora?
What is TempoDB?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose TempoDB?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using TempoDB?
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
Over the years we have added a wide variety of different storages to our stack including PostgreSQL (some hosted by Heroku, some by Amazon RDS) for storing relational data, Amazon DynamoDB to store non-relational data like recommendations & user connections, or Redis to hold pre-aggregated data to speed up API endpoints.
Since we started running Postgres ourselves on RDS instead of only using the managed offerings of Heroku, we've gained additional flexibility in scaling our application while reducing costs at the same time.
We are also heavily testing Amazon RDS for Aurora in its Postgres-compatible version and will also give the new release of Aurora Serverless a try!
#SqlDatabaseAsAService #NosqlDatabaseAsAService #Databases #PlatformAsAService
Back in 2014, I was given an opportunity to re-architect SmartZip Analytics platform, and flagship product: SmartTargeting. This is a SaaS software helping real estate professionals keeping up with their prospects and leads in a given neighborhood/territory, finding out (thanks to predictive analytics) who's the most likely to list/sell their home, and running cross-channel marketing automation against them: direct mail, online ads, email... The company also does provide Data APIs to Enterprise customers.
I had inherited years and years of technical debt and I knew things had to change radically. The first enabler to this was to make use of the cloud and go with AWS, so we would stop re-inventing the wheel, and build around managed/scalable services.
For the SaaS product, we kept on working with Rails as this was what my team had the most knowledge in. We've however broken up the monolith and decoupled the front-end application from the backend thanks to the use of Rails API so we'd get independently scalable micro-services from now on.
Our various applications could now be deployed using AWS Elastic Beanstalk so we wouldn't waste any more efforts writing time-consuming Capistrano deployment scripts for instance. Combined with Docker so our application would run within its own container, independently from the underlying host configuration.
Storage-wise, we went with Amazon S3 and ditched any pre-existing local or network storage people used to deal with in our legacy systems. On the database side: Amazon RDS / MySQL initially. Ultimately migrated to Amazon RDS for Aurora / MySQL when it got released. Once again, here you need a managed service your cloud provider handles for you.
Future improvements / technology decisions included:
Caching: Amazon ElastiCache / Memcached CDN: Amazon CloudFront Systems Integration: Segment / Zapier Data-warehousing: Amazon Redshift BI: Amazon Quicksight / Superset Search: Elasticsearch / Amazon Elasticsearch Service / Algolia Monitoring: New Relic
As our usage grows, patterns changed, and/or our business needs evolved, my role as Engineering Manager then Director of Engineering was also to ensure my team kept on learning and innovating, while delivering on business value.
One of these innovations was to get ourselves into Serverless : Adopting AWS Lambda was a big step forward. At the time, only available for Node.js (Not Ruby ) but a great way to handle cost efficiency, unpredictable traffic, sudden bursts of traffic... Ultimately you want the whole chain of services involved in a call to be serverless, and that's when we've started leveraging Amazon DynamoDB on these projects so they'd be fully scalable.
Managed MySQL clustered database so I dont have to deal with the required infrastructure
Core database for managing users, teams, tests, and result summaries
We moved our database from compose.io to AWS for speed and price.