Hydra provides tools to reduce boilerplate code and dynamically compose configurations for applications, facilitating rapid experimentation and integration with various infrastructures. Self-described as enabling plugins for cloud providers.

Hydra

Hydra | 1,699 followers on LinkedIn. DuckDB-Powered Postgres for real-time apps and analytics. | Hydra is the easiest way to build real-time apps and analytics with Postgres.

Every project with Hydra uses pg_duckdb, an open source (MIT licensed) program that embeds DuckDB&#39;s state-of-the-art analytics engine and features within Postgres. We developed pg_duckdb, the official Postgres extension for DuckDB, in collaboration with the DuckDB Foundation.

Michael Farnbach

Hacker: github.com/owenthereal

Jingwen Owen Ou

Co-founder & CEO at Hydra

Joseph Sciarrino

Founder at Hydra Powders

Lauren Boultier

Postgres analytics 10x faster with just an extension?! 🤯 In August, we announced pg_duckdb, a PostgreSQL extension that integrates DuckDB's analytics engine directly into Postgres. It's open-source and represents a joint partnership between Hydra and MotherDuck. Two months later, we are happy to announce its first release and highlight many features, including the ability to read and write over object storage with Parquet and CSV, as well as Apache Iceberg (currently read-only), and the capability to query from MotherDuck without leaving Postgres. Check out the blog for more snippets, and start quacking around! https://lnkd.in/eajf22BD

MotherDuck

Problem: Slow analytics queries in Postgres 🕝 Solution: Turn on DuckDB execution with pg_duckdb! 🦆 3 min. demo presented by Joseph Sciarrino . #DuckDB #PostgreSQL

Splicing duck and elephant DNA? We're helping put DuckDB in Postgres as an open source project owned by DuckDB Foundation. https://lnkd.in/gfbrrEc9

Introducing pg_quack - 🦆 duckdb in Postgres pg_quack is a Postgres extension that uses DuckDB’s engine to make Postgres faster than Snowflake and improves Postgres’ analytical query performance by over 100X. pg_quack is an experimental project built in 48 hours at Hydra. pg_quack is Apache 2.0 open source! 🎉 You can try pg_quack in ~10 seconds using brew or curl with pgxman- “npm for Postgres extensions.” > brew install pgxman/tap/pgxman or > curl -sfL https://install.pgx.sh | sh - run: > pgxman install pg_quack 🎉 get quackin’ with Postgres 🦆🦆

https://docs.hydra.so/ Check out our simplified install instructions for macOS, linux, cloud, to add a columnar analytics engine to your Postgres in 10 seconds! We use the Postgres Extension Manager "pgxman" as package manager and extension registry to makes install, upgrade, and management delightful. Using an extension manager makes it easy to discover and use Postgres’ full capabilities for app development.

Meet Hydra 1.1 - our open source columnar Postgres extension, now with upsert and Postgres 16 support. 🎉 Upsert, also known as "INSERT ... ON CONFLICT", is a feature in PostgreSQL that let's a user insert a new record or update an existing one if it already exists, using a single command. Upsert is useful in several ways: 1. Data Consistency: It manages and keeps the data clean and free of redundancies. Any attempt to insert a new row of data into an existing table is modified into update commands when a conflict occurs. 2. Simplified Queries: Instead of writing separate INSERT and UPDATE queries, with Upsert, you can both cases in a single query thereby reducing the complexity. 3. Efficiency: Since a single statement can handle the process of inserting a new row or updating an existing one, the number of queries processed by the server can be reduced. 4. Atomicity: Upsert operations are atomic, meaning they will either fully complete or fully fail, ensuring the data integrity is maintained. 5. Error Handling: It prevents the processing from being halted due to error thrown if data already exists. In a large batch operation, this is especially useful.

Introducing "pgxman" - npm for Postgres extensions RELEASE BLOG: https://lnkd.in/gb9KjxDz pgxman simplifies the discovery and use of extensions so full stack developers can easily enhance the capabilities of their applications. Instead of managing extension versions, build & run dependencies, operating system, platform architecture, pgxman automatically detects and streamlines extension operations (xOps) based on the local development environment. Without pgxman, installing and updating extensions can be an uphill battle. You're left searching for the right build tools and grappling with often unclear and incomplete compiling instructions to even try one out. But with pgxman, we've streamlined the process to one simple step: > pgxman install [extension name] pgxman integrates with the system package manager, ensuring the correct versions are installed without extra packages from any shared dependencies between extensions. pgxman’s automated build system creates [APT] packages for each Postgres version, platform, and OS supported by the extension. Extensions are built from a “buildkit” formula, written in YAML, and are contributed through GitHub.

HYDR

CC:HYDRA

Hydra