Amazon RDS vs TempoDB: What are the differences?
Amazon RDS: Set up, operate, and scale a relational database in the cloud. Amazon RDS gives you access to the capabilities of a familiar MySQL, Oracle or Microsoft SQL Server database engine. This means that the code, applications, and tools you already use today with your existing databases can be used with Amazon RDS. Amazon RDS automatically patches the database software and backs up your database, storing the backups for a user-defined retention period and enabling point-in-time recovery. You benefit from the flexibility of being able to scale the compute resources or storage capacity associated with your Database Instance (DB Instance) via a single API call; TempoDB: 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 and TempoDB can be primarily classified as "SQL Database as a Service" tools.
Some of the features offered by Amazon RDS are:
- Pre-configured Parameters
- Monitoring and Metrics
- Automatic Software Patching
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?
What is TempoDB?
Want advice about which of these 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 Amazon RDS?
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
While we initially started off running our own Postgres cluster, we evaluated RDS and found it to be an excellent fit for us.
The failovers, manual scaling, replication, Postgres upgrades, and pretty much everything else has been super smooth and reliable.
We'll probably need something a little more complex in the future, but RDS performs admirably for now.
We are using RDS for managing PostgreSQL and legacy MSSQL databases.
Unfortunately while RDS works great for managing the PostgreSQL systems, MSSQL is very much a second class citizen and they don't offer very much capability. Infact, in order to upgrade instance storage for MSSQL we actually have to spin up a new cluster and migrate the data over.
Our PostgreSQL servers, where we keep the bulk of Wirkn data, are hosted on the fantastically easy and reliable AWS RDS platform.
We use Aurora for our OLTP database, it provides significant speed increases on top of MySQL without the need to manage it