Skip to main content

general sugarcoat for all pubsub flavors.

Project description

tesselite-pubsub

ci cd

General sugarcoat for all pubsub flavors.

purpose

Publish Subscribe is a pretty simple mechanism understandable by any human. For example, it is the ruling mechanism of all social networks.

But, in Python, pubsub is very complex to code given the variety of broker technologies (redis, rabbitMQ, kafka, GCP PubSub, Azure Event Hubs..)

The purpose of this library is to streamline the coding of Pubsub in a single-line call!

usage

Available Brokers:

internal name official name client library
gcp-pubsub Goggle Cloud Pubsub google-cloud-pubsub = "^2.26.1"
redis Redis redis = "^5.1.1"
rabbitmq RabbitMQ pika = "^1.3.2"

Not available Brokers:

internal name official name client library
kafka Apache Kafka todo

low level usage

consume

from tesselite.pubsub import pubsubFactory

def callback(message): # callback function inputs serialized message 
    print(f"received this: {message}")
    
# consume loop
with pubsubFactory(broker="gcp-pubsub")(topic="tesselite-pubsub", log_name="consumer") as pubsub:
    pubsub.consume(callback=callback, deadLetter=None, subscription="tesselite")

publish

from tesselite.pubsub import pubsubFactory

def encoder(): # callback function inputs serialized message 
    yield "hello world"
    
# publish loop
with pubsubFactory(broker="gcp-pubsub")(topic="tesselite-pubsub", log_name="publisher") as pubsub:
    for msg in encoder():
        pubsub.publish(msg)

high level usage

consume

from tesselite.samples import consume # importing consume sample


def callback(message): # callback function inputs serialized message 
    print(f"received this: {message}")

if __name__ == '__main__':
    consume(broker='rabbitmq', callback=callback) # single-lined consume loop (default topic: tesselite-pubsub

publish

from tesselite.samples import publish # importing publish sample


def encoder(): # callback function inputs serialized message 
    yield "hello"

if __name__ == '__main__':
    publish(broker='rabbitmq', encoder=encoder) # single-lined publish call (default topic: tesselite-pubsub

behavior

Best Case Scenario

All broker backends technology implements the same interface → One would swap seamlessly to any broker technology by shifting the broker's name:

from tesselite import pubsubFactory

# broker : rabbitmq
client_gcp = pubsubFactory(broker="rabbitmq")(topic="tesselite-pubsub", log_name="tesselite")

# broker : redis
client_redis = pubsubFactory(broker="redis")(topic="tesselite-pubsub", log_name="tesselite")

The connection to broker auto-heals when the broker backend is unavailable → When auto-healing happens the log trace looks like this:

[tesselite][ERROR][2024-10-28 06:22:07] (open) connexion error [ConnectionError] => backoff.
[tesselite][ERROR][2024-10-28 06:22:13] (open) connexion error [ConnectionError] => backoff.
[tesselite][ERROR][2024-10-28 06:22:21] (open) connexion error [ConnectionError] => backoff.
[consume][INFO][2024-10-28 06:22:29] ready.
received this: {"uid": 0, "payload": "( publish ) hello world!"}
received this: {"uid": 1, "payload": "( publish ) hello world!"}
received this: {"uid": 2, "payload": "( publish ) hello world!"}

The procedure below is applied seamlessly to all broker technologies → To guarantee a fail-proof onboarding to the broker:

  1. topic checkout
  2. topic creation
  3. subscription checkout
  4. subscription creation
  5. publish or consume

Worst Case Scenario

A) Messages are lost if the subscription doesn't exist → This is an incurable limitation of pubsub mechanics.

B) The broker redis would drop messages if the consumer disconnects → This seems to be related to 'livestream' behavior of Redis.

C) The broker gcp-pubsub would freeze for a random timeperiod if no messages are available → This would generate sluggishness from time to time.

Therefore, the broker redis is ideal for livestreaming but not for message retention critical PaaS.

Therefore, the broker gcp-pubsub is ideal for message retention critical PaaS but maybe sluggish for livestream.

releases

Notes

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

tesselite_pubsub-0.2.0.tar.gz (10.2 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

tesselite_pubsub-0.2.0-py3-none-any.whl (12.3 kB view details)

Uploaded Python 3

File details

Details for the file tesselite_pubsub-0.2.0.tar.gz.

File metadata

  • Download URL: tesselite_pubsub-0.2.0.tar.gz
  • Upload date:
  • Size: 10.2 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: poetry/1.8.4 CPython/3.12.7 Linux/6.5.0-1025-azure

File hashes

Hashes for tesselite_pubsub-0.2.0.tar.gz
Algorithm Hash digest
SHA256 9e87609870ca192363b0ea22b769e2b81a495cd0080bf516a495384c656eb0fb
MD5 5817bd416eb4cdb9dfe2ec30050fc9e8
BLAKE2b-256 9892fd87aff6c8f28ad58a5d69fd20219d958a9656733a718ec411a9b33e7c13

See more details on using hashes here.

File details

Details for the file tesselite_pubsub-0.2.0-py3-none-any.whl.

File metadata

  • Download URL: tesselite_pubsub-0.2.0-py3-none-any.whl
  • Upload date:
  • Size: 12.3 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: poetry/1.8.4 CPython/3.12.7 Linux/6.5.0-1025-azure

File hashes

Hashes for tesselite_pubsub-0.2.0-py3-none-any.whl
Algorithm Hash digest
SHA256 0bd714feb896d017c058ae38a10ef0c26983fe090dd8e71905678b9378f5aa01
MD5 fe974483bb66533e3d6df9ab7580da0d
BLAKE2b-256 bde5bcc1637692f9da42938dbd45bf6f1c6b53b192ab2d89ffa32edf09e71f31

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page