redis-om-node
spec
Our great sponsors
redis-om-node | spec | |
---|---|---|
19 | 62 | |
1,110 | 8,627 | |
2.8% | 2.4% | |
7.5 | 0.0 | |
6 months ago | 3 months ago | |
TypeScript | ||
MIT License | GNU General Public License v3.0 only |
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.
redis-om-node
-
A simpler ORM than TypeORM/Prisma/Mongoose?
How about using Redis OM https://github.com/redis/redis-om-node
-
Passwordless Authentication in Node.js on Redis
In the code above, you could see some SQL-like query structure which makes the entire thing very friendly, this is made possible by Redis-om which is a new Redis client from Redis
-
Building a Fullstack App with NodeJS, ExpressJs and Redis-OM
Redis-OM Node Github Repo
-
Ephemeral Chats
Welcome to Ephemeral Chats, a TypeScript NodeJS app made with NestJS, Apollo GraphQL, RedisOM and MikroORM.
-
Redis-OM Lambda CDK
This sample shows how to define a Lambda function which uses Redis-om via AWS Cloud Development Kit. This is a fork of prisma-lambda-cdk sample repo which replaces mysql/postgres with redis stack & prisma with Redis-om.
-
Stoa - forum app that use redis as a primary database
Fast integration thanks to redis-om-node library. In dozen minutes, we are ready to start manipulating with documents.
-
How to use Redis as a Database using Node.js
The next step will be to create the entity and schema of our api (to be simpler I put it in the same file as the database configuration):
-
Quiz app in Next JS and Redis
For the database, our app used Redis Database as the primary database for storage of information of users and quizzes. In order to interact with the redis database, we utilized Redis-OM, a Node JS library for redis that enables storage of JSON objects in Redis database. It also gives access to native redis-cli commands such as saving cache in redis directly which was pretty handy when storing questions in Redis cache whenever a student is taking a quiz and marking correct responses from a student.
-
Snapsend - Send limited photos to your friends is easier than ever
Redis OM
-
Next.Js Crowd: See Who Talks About The React Framework
Redis Om for Node - Object mapping, and more, for Redis and Node.js. Written in TypeScript. https://github.com/redis/redis-om-node
spec
-
The UX of UUIDs
Can use ULID to "fix" some issues
https://github.com/ulid/spec
- Ulid: Universally Unique Lexicographically Sortable Identifier
-
Ask HN: Is it acceptable to use a date as a primary key for a table in Postgres?
Both ULID and UUID v7 have a time code component which can be extracted.
It would be best for indexing to store the actual value in binary, though not strictly necessary as these later UUID standards (unlike conventional UUIDs) use time code prefixes (so indexing clusters.)
https://uuid7.com/
https://github.com/ulid/spec
-
Bye Sequence, Hello UUIDv7
UUIDv7 is a nice idea, and should probably be what people use by default instead of UUIDv4.
For the curious:
* UUIDv4 are 128 bits long, 122 bits of which are random, with 6 bits used for the version. Traditionally displayed as 32 hex characters with 4 dashes, so 36 alphanumeric characters, and compatible with anything that expects a UUID.
* UUIDv7 are 128 bits long, 48 bits encode a unix timestamp with millisecond precision, 6 bits are for the version, and 74 bits are random. You're expected to display them the same as other UUIDs, and should be compatible with basically anything that expects a UUID. (Would be a very odd system that parses a UUID and throws an error because it doesn't recognise v7, but I guess it could happen, in theory?)
* ULIDs (https://github.com/ulid/spec) are 128 bits long, 48 bits encode a unix timestamp with millisecond precision, 80 bits are random. You're expected to display them in Crockford's base32, so 26 alphanumeric characters. Compatible with almost everything that expects a UUID (since they're the right length). Spec has some dumb quirks if followed literally but thankfully they mostly don't hurt things.
* KSUIDs (https://github.com/segmentio/ksuid) are 160 bits long, 32 bits encode a timestamp with second precision and a custom epoch of May 13th, 2014, and 128 bits are random. You're expected to display them in base62, so 27 alphanumeric characters. Since they're a different length, they're not compatible with UUIDs.
I quite like KSUIDs; I think base62 is a smart choice. And while the timestamp portion is a trickier question, KSUIDs use 32 bits which, with second precision (more than good enough), means they won't overflow for well over a century. Whereas UUIDv7s use 48 bits, so even with millisecond precision (not needed) they won't overflow for something like 8000 years. We can argue whether 100 years us future proof enough (I'd argue it probably is), but 8000 years is just silly. Nobody will ever generate a compliant UUIDv7 with any of the first several bits aren't 0. The only downside to KSUIDs is the length isn't UUID compatible (and arguably, that they don't devote 6 bits to a compliant UUID version).
Still feels like there's room for improvement, but for now I think I'd always pick UUIDv7 over UUIDv4 unless there's an very specific reason not to.
-
50 years later, is Two-Phase Locking the best we can do?
I'd love for Postgres to adopt ULID as a first class variant of the same basic 128bit wide binary optimized column type they use for UUIDs, but I don't expect they will, while its "popular" its not likely popular enough to have support for them to maintain it in the long run... Also the smart money ahead of time would have been for the ULID spec to sacrifice a few data bits to leave the version specifying sections of the bit field layout unused in the ULID binary spec (https://github.com/ulid/spec#binary-layout-and-byte-order) for the sake of future compatibility with "proper" UUIDs... Performing one big bulk bitfield modification to a PostgreSQL column would have been much less painful than re-computing appropriate UUIDv7 (or UUIDv8s for some reason) and then having to perform a primary key update on every row in the table.
- FLaNK Stack Weekly for 12 September 2023
- You Don't Need UUID
- UUID Collision
-
Type-safe, K-sortable, globally unique identifier inspired by Stripe IDs
Many people had the same idea. For example ULID https://github.com/ulid/spec is more compact and stores the time so it is lexically ordered.
- ULID: Universally Unique Lexicographically Sortable Identifier
What are some alternatives?
mantine - A fully featured React components library
dynamodb-onetable - DynamoDB access and management for one table designs with NodeJS
redis-om-python - Object mapping, and more, for Redis and Python
uuid6-ietf-draft - Next Generation UUID Formats
redis-om-spring - Spring Data Redis extensions for better search, documents models, and more
kuuid - K-sortable UUID - roughly time-sortable unique id generator
nextjs-crowd - NextJs Crowd monitors Twitter for users that mention the react framework Next.js and it shows some daily stats like "top users", "top tweets", etc
python-ksuid - A pure-Python KSUID implementation
redis-om-dotnet - Object mapping, and more, for Redis and .NET
ulid-lite - Generate unique, yet sortable identifiers
RedisInsight - Redis GUI by Redis
shortuuid.rb - Convert UUIDs & numbers into space efficient and URL-safe Base62 strings, or any other alphabet.