Skip to main content

relations-redis

DB/API Modeling for Redis

Relations overall is designed to be a simple, straight forward, flexible DIL (data interface layer).

Quite different from other DIL's, it has the singular, microservice based purpose to:

  • Create models with very little code, independent of backends
  • Create CRUD API with a database backend from those models with very little code
  • Create microservices to use those same models but with that CRUD API as the backend

Ya, that last one is kinda new I guess.

Say we create a service, composed of microservices, which in turn is to be consumed by other services made of microservices.

You should only need to define the model once. Your conceptual structure is the same, to the DB, the API, and anything using that API. You shouldn't have say that structure over and over. You shouldn't have to define CRUD endpoints over and over. That's so boring, tedious, and unnecessary.

Furthermore, the conceptual structure is based not the backend of what you've going to use at that moment of time (scaling matters) but on the relations, how the pieces interact. If you know the structure of the data, that's all you need to interact with the data.

So with Relations, Models and Fields are defined independent of any backend, which instead is set at runtime. So the API will use a DB, everything else will use that API.

This is just the Redis backend of models and what not.

Unlike the SQL backends, Redis is a key-value store with no query engine. Each record is stored as one JSON string keyed by <prefix>:<model>:<id>, with an atomic INCR counter allocating ids. Id-based reads/writes/deletes are direct GET/SET/DEL; any other filter is resolved client-side by scanning the model's keys and matching in Python (the same record matcher every backend uses) — so the model-facing API is identical, but a non-id filter is a full scan rather than an indexed query.

Don't have great docs yet so I've included some of the unittests to show what's possible.

Example

define

import relations
import relations_redis

# The source is a string, the backend of which is defined at runtime

class SourceModel(relations.Model):
    SOURCE = "RedisSource"

class Simple(SourceModel):
    id = int
    name = str

class Plain(SourceModel):
    ID = None # This table has no primary id field
    simple_id = int
    name = str

# This makes Simple a parent of Plain

relations.OneToMany(Simple, Plain)

# With this statement, all the above models now have this Redis as a backend.
# Redis is schemaless, so there's no define()/migrate() step — just connect.

self.source = relations_redis.Source("RedisSource", host="localhost", port=6379)

create

simple = Simple("sure")
simple.plain.add("fine")

simple.create()

self.assertEqual(simple.id, 1)
self.assertEqual(simple._action, "update")
self.assertEqual(simple._record._action, "update")
self.assertEqual(simple.plain[0].simple_id, 1)
self.assertEqual(simple.plain._action, "update")
self.assertEqual(simple.plain[0]._record._action, "update")

# Each record is one JSON string keyed by <prefix>:<model>:<id>

self.assertEqual(
    json.loads(self.source.connection.get("simple:1")),
    {"id": 1, "name": "sure"}
)

simples = Simple.bulk().add("ya").create()
self.assertEqual(simples._models, [])

self.assertEqual(
    json.loads(self.source.connection.get("simple:2")),
    {"id": 2, "name": "ya"}
)

self.assertEqual(
    json.loads(self.source.connection.get("plain:1")),
    {"simple_id": 1, "name": "fine"}
)

Release files for relations-redis 0.2.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for relations-redis 0.2.3
File Size Uploaded
relations_redis-0.2.3.tar.gz 10.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for relations-redis 0.2.3
File Interpreter ABI Platform
relations_redis-0.2.3-py3-none-any.whl Python 3 none any Details

Total release size: 17.6 kB

Release files / relations_redis-0.2.3.tar.gz

Download URL relations_redis-0.2.3.tar.gz
Size 10.5 kB
Tags Source
SHA-256 checksum
How to use checksums
a5a3f05f118cb323993950a0c608da30c47370aef846df225b7bc8fddb66d83d
BLAKE2b-256 checksum
How to use checksums
95b937b11fe73e8cf29f84fca8b1c8ab906527a7ac222cf1c8ad0b3d1ee1f33a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.1 CPython/3.8.5

Release files / relations_redis-0.2.3-py3-none-any.whl

Download URL relations_redis-0.2.3-py3-none-any.whl
Size 7.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8742b20963c631fbd3c05962d44b575baf9c16d551770bc9bb35d9e838fee527
BLAKE2b-256 checksum
How to use checksums
55cd56e2cc5c5a462e6953f0139027da285dad83ce22f131c9560ab9f8344f27
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.1 CPython/3.8.5

Release history Release notifications | RSS feed

This release

0.2.3 This release

2 release files

0.2.2

2 release files

0.2.1

2 release files

0.2.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page