js-id
postgres-elasticsearch-fdw
Our great sponsors
js-id | postgres-elasticsearch-fdw | |
---|---|---|
3 | 3 | |
10 | 104 | |
- | - | |
5.9 | 0.0 | |
7 months ago | 16 days ago | |
TypeScript | Python | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
js-id
-
Type-safe, K-sortable, globally unique identifier inspired by Stripe IDs
We have a uuidv7 implementation that we've been using with rocksdb for over a year https://github.com/matrixai/js-id
-
Plan B for UUIDs: double AES-128
We evaluated ULID but we wanted something that is future proof for our decentralised secret sharing system. So we implemented UUIDv7 in TypeScript called `IdSortable` https://github.com/MatrixAI/js-id
It allows strict monotonic IDs when you provide it the previously generated ID. The resulting data structure is a Uint8Array making it easy to put into binary structures. Can also be used as a key inside any POJO record.
-
Lesser Known PostgreSQL Features
I had reviewed existing UUIDv7 implementations and many were incorrect or had subtle timing bugs.
We ended up implementing UUIDv7 in our ID generation library https://github.com/MatrixAI/js-id. And we have a number of tests ensuring that it is truly monotonic even across process restarts.
See IdSortable.
postgres-elasticsearch-fdw
- Full-text search engine with PostgreSQL (part 2): Postgres vs. Elasticsearch
-
Postgres Full Text Search vs. the Rest
My experience with Postgres FTS (did a comparison with Elastic a couple years back), is that filtering works fine and is speedy enough, but ranking crumbles when the resulting set is large.
If you have a large-ish data set with lots of similar data (4M addresses and location names was the test case), Postgres FTS just doesn't perform.
There is no index that helps scoring results. You would have to install an extension like RUM index (https://github.com/postgrespro/rum) to improve this, which may or may not be an option (often not if you use managed databases).
If you want a best of both worlds, one could investigate this extensions (again, often not an option for managed databases): https://github.com/matthewfranglen/postgres-elasticsearch-fd...
Either way, writing something that indexes your postgres database into elastic/opensearch is a one time investment that usually pays off in the long run.
-
Lesser Known PostgreSQL Features
I used a foreign data wrapper to query elasticsearch indexes from within postgres.[0]
It pushed alot of complexity down away from higher-level app developers not familiar with ES patterns.
[0]: https://github.com/matthewfranglen/postgres-elasticsearch-fd...
What are some alternatives?
rum - RUM access method - inverted index with additional information in posting lists
tbls - tbls is a CI-Friendly tool for document a database, written in Go.
pg-ulid - ULID Functions for PostgreSQL
ksuid - K-Sortable Globally Unique IDs
typeid - Type-safe, K-sortable, globally unique identifier inspired by Stripe IDs
typeid-go - Go implementation of TypeIDs: type-safe, K-sortable, and globally unique identifiers inspired by Stripe IDs
pgvector - Open-source vector similarity search for Postgres
postgres-elasticsearch-fd
resource-id - Developer-friendly k-sortable IDs
rust-ksuid - A pure-Rust KSUID implementation
afid