1/5. @paradedb has raised a $12M Series A to bring Elasticsearch workloads to Postgres. 🧵 https://t.co/L2BroGIQlR

Announcing Railway partnerships 🤝 Companies & OSS tools in our partner program get - Verified templates - Revshare - Telemetry Launching with: @Redisinc @bunjavascript @prisma @posthog @DrizzleORM @calcom @WaspLang @paradedb @resend @xata @falkordb https://t.co/RgPLwgSfRK

Interesting article on how Target built search on Postgres. Can get quite far with just regular Postgres FTS:

Interesting article on narrowing the use case to find PMF:

Unintended side effects of starting a Postgres company: I now have 4 elephant plushies (I purchased none of them) 🐘

3/3. We've done a deep dive into when to use Postgres logical replication and when to use ETL when working with a Postgres source. Let me know what you think!

2/3. There's a time and place for ETL. They're amazing tools. But in Postgres world, there's something called logical replication that enables sync-ing two Postgres databases in real-time. Should you use it?

1/3. ETL: no company's favorite tool, every company's necessary evil. Synchronizing Postgres to Elasticsearch/OpenSearch is an incredibly common workflow, usually via an ETL tool like Kafka+Debezium. But what if you had another option?

A great blog post by the folks at Feldera on testing a strongly-consistent, core infrastructure system. We use many of the same ideas at ParadeDB (especially proptesting):

I’m convinced that anyone who says Thinking Fast and Slow is a good book is just trying to masquerade as erudite and sophisticated Nothing against Kahneman, but that brick is literally 500 pages of word vomit that could’ve been said in two paragraphs

I'm like a kid on Christmas Eve thinking about the new people that are joining us at ParadeDB next week. Stay tuned 🤩

"A normalized data model allowed us to have a 10x reduction in write workload compared to the denormalized data model that we had to use in Elasticsearch. This led to substantial savings on storage and indexing." Why Instacart picked Postgres for search:

Very useful, my team and I weren't even aware of this one. Thank you @eatonphil!

ParadeDB just reached 70 contributors. I spent some time reflecting on what brings people to contribute to open-source projects. Lmk what you think: https://t.co/lUXNVgKR8F

The future is Postgres (and Rust): https://t.co/d6YcLWG8fa

4/4. We'll be highlighting more of our customer partnerships over the next few months. If you're sync-ing data between Postgres and a search engine like Elasticsearch (or thinking about doing so), we'd love to talk.

3/4. ParadeDB has been running in production with Bilt for several months, and we couldn't be prouder to help them improve the shopping and neighborhood experience for so many in the US.

2/4. Bilt deployed ParadeDB within their GCP environment and connected directly to their existing Postgres clusters. No ETL tool, no denormalization, all real-time.

1/4. I'm incredibly excited for this case study to come out. The @paradedb and @BiltRewards teams have been working together to take Bilt's user-facing search experience to the next level, all without the cumbersome infrastructure of a bespoke search database.

Thank you @paradedb for sponsoring Lindera and me on @github. 企業スポンサーがついてくれた。うれしい。 https://t.co/haw6uiCzlI

very tidy write-up from the @paradedb team (they do search, inside postgres - worth a look)