Home / Companies / Tiger Data / Blog / January 2024

January 2024 Summaries

7 posts from Tiger Data

Filter
Month: Year:
Post Summaries Back to Blog
Live migrations is a battle-tested, almost zero downtime migration strategy for Timescale that simplifies the transition process to Timescale, even for large PostgreSQL databases. It leverages logical decoding using pgcopydb to ensure changes made to the source database are applied to the target database in real-time without significant downtime. The process involves creating a replication slot, buffering historical data and live changes into disk, and then applying these changes to the target database. To achieve seamless migration, it is essential to set up environment variables, configure pgcopydb correctly, and perform thorough validation of the migrated data. With live migrations, users can migrate their terabyte-scale PostgreSQL databases to Timescale without significant downtime, ensuring minimal disruption to their applications. The solution is designed for heavy workloads and provides best-in-class performance and reliability for future migrations.
Jan 29, 2024 3,949 words in the original blog post.
The author of this tutorial rebuilt a data pipeline on top of TimescaleDB to fetch and transform sensor data readings from remote locations. They adapted Django, a Python web framework, to play nicely with the database by creating a custom API and views. The author implemented an import method that can handle messy files with varying formats and field names, using techniques such as parsing JSON files, validating file contents, and utilizing TimescaleDB's hypertable feature for efficient data storage. By leveraging Celery, a task queue library, they improved performance by offloading file imports to a separate process, allowing the main application to remain responsive during uploads. The tutorial showcases how Django can be used to create a robust web application that seamlessly integrates with TimescaleDB for fast and efficient data analysis.
Jan 19, 2024 3,539 words in the original blog post.
Amazon Aurora is a managed database service designed to simplify database setup and management, providing performance gains, fault tolerance, and increased security compared to open-source variants of MySQL and PostgreSQL. It offers features such as serverless deployment, global databases, and automatic scaling, making it suitable for unpredictable or bursty workloads. To estimate costs accurately, users need to define their application architecture, calculate data storage and throughput needs, determine Aurora usage type and contract type, and consider additional feature costs. The AWS Pricing Calculator is recommended for estimating potential costs, and users should also monitor costs and set up billing alerts to ensure transparency and predictability. Additionally, Timescale offers a simpler pricing model with two elements: compute and storage, making it transparent and predictable, especially for time-series data and demanding workloads.
Jan 17, 2024 1,860 words in the original blog post.
PostgreSQL aggregates and hyperfunctions' design is centered around enhancing developer experience. The PostgreSQL aggregate API works row-by-row, storing state about previous rows and updating it as new rows are seen. This can lead to performance issues if not optimized. To address this, TimescaleDB's two-step aggregation design pattern was developed, which separates the aggregate function from its accessor, allowing for better optimization and logical consistency in re-aggregation. This approach enables features such as deduplication, rollups, and retrospective analysis of downsampled data, making it easier for developers to work with large datasets. The design also allows for flexibility in continuous aggregates, enabling users to modify parameters without recalculating old states.
Jan 11, 2024 4,924 words in the original blog post.
To migrate from an AWS RDS for PostgreSQL database to a high-performance, cost-effective, and predictable PostgreSQL database with Timescale, developers can use the live migration solution provided by Timescale. This process involves several steps including assessing the current database size, complexity, and dependencies, planning a migration strategy, enabling hypertables on time-series tables, migrating data from the old database to the new one with minimal downtime, testing the new database with applications, and cutovering to the target database. The recommended approach is to use an intermediate machine to execute the migration process, utilizing tools like pg_dump/pg_restore and PostgreSQL logical decoding for a seamless transition. By following this playbook, developers can achieve 44% faster data ingestion, up to 350x faster queries, and 95% storage savings compared to RDS.
Jan 09, 2024 1,899 words in the original blog post.
PostgreSQL is a robust and versatile database management system that offers advanced features like custom data types and efficient write operations, making it ideal for complex and large-scale applications such as e-commerce platforms and financial systems. MySQL, on the other hand, is known for its simplicity and efficiency, catering well to more straightforward, static systems where speed and ease of use are essential. The choice between PostgreSQL and MySQL ultimately depends on the project's specific scale and operational intricacy needs, with PostgreSQL being a better fit for projects that demand the handling of voluminous or complex data.
Jan 04, 2024 2,376 words in the original blog post.
This tutorial guides you through creating a cryptocurrency market dataset using Python, CryptoCompare API, and PostgreSQL. The steps covered include setting up a TimescaleDB instance in the cloud, defining a schema for cryptocurrency data, fetching historical prices of Bitcoin (BTC) and Ethereum (ETH), loading the data into TimescaleDB, querying the data using SQL, and visualizing the results with Tableau. The final dataset can be used to analyze various aspects of the cryptocurrency market such as price trends, trading volumes, and more.
Jan 04, 2024 4,234 words in the original blog post.